I have written several of these for clients and this is like taking up cliff
diving because you want to learn to swim!
Here are some comments
1. You need a set of tables that track employees (employeeID,
employeeFirstName,EmployeeMiddleName,EmployeeLastName,Employee......)
2. You need a set of tables that track the employees employment history
(EmploymentID, DateStart,DateEnd,Position, Other stuff depends on the
situation)
note: employees come and go then come back and some companies will
let them come back with some portion of their leave in tact others will not.
3. You need a set of tables that track the employees leave usage
(employeeID, LeaveUsageID, date, type,length of time)
note: some employees work on number of days (don't allow 1/2 day)
others work on Hours basis.
4. You need a set of tables that track the types of leave you will be
following (e.g. LeaveTypeID, LeaveTypeText)
note: simple examples are sick leave and annual leave but I have run
into things like educational leave, family leave, reserve training leave,
etc. ....
5. You need a set of table relationships that tie all above together to
maintain data integerity.
6. You need a set of VBA code that caputures the "Business Rules" for the
award, removal, carryover, etc of leave.
7. You need a set of forms to fill in all of the above
8. You need a set of reports to print out the information like leave
statements for the individuals etc.
Note within one organization I work with I have five different versions
running because they have different rules for leave in each department (it
is up to the department head how he/she interperts the rules).
I hope the above will give you a starting point, you may be able to simplify
your specific application enough to build something to start with. I do
encourage you to jump in and build something. Access is simple and
complicated at the same time. I had to jus start with something I wanted to
build, build it, then start over with what I had learned in the process.
Cheers,
Ed Warren