The design of an annual attendance statistics system first adds information pages by month: including employee name, year, month, late, absenteeism, warning... for some columns, the page is displayed by month. employee names are as follows: January, January, and January... late in March, absent from work, warning... the number of times. The last step is to count the total number of times of year, late, absenteeism, warning. The specific design is like this. I hope you will have comments and ideas !!! Thank you! ----- Design of an annual attendance statistics system
First, add the information page by month:
Including employee name, year, month, late, absenteeism, warning...
Next, display the page by month:
Employee name: The following are the numbers of late, absenteeism, and warnings in January, January, and January.
The last step is to count the total number of times of year, late, absenteeism, warning.
The specific design is like this. I hope you will have comments and ideas !!!
Thank you!
------ Solution --------------------
The monthly, yearly, individual, quarterly, or departmental statistics are based on attendance table data.
As long as your attendance table has these raw data records.
The rest is about reports, that is, about writing SQL statements. There are no design issues.
The attendance table has the following fields for statistics:
Employee id, department, violation type (late, absenteeism, warning), violation time.
We recommend that you write a stored procedure (fast) and then call it to return to the presentation layer.
