holiday database

[Guest]

I would like to build a database to keep track of employees' holidays and
absences. At the moment we have a paper form for each employee with 365
boxes/cells (Month name going down and day number going along). A code is
inserted into one of these boxes depending on what the person is doing in the
year (ie absent, paid holiday etc).
How could I create a database to do this for each holiday?

 

[kingston via AccessMonster.com]

There are a lot of ways to do this. Here's just one:

Create three tables: Employee, Holidays, Personal
Employee lists all employee information and assigns a unique ID to each
person.
Holidays lists all of the fixed holidays (weekends) that apply to everyone.
Personal is where you keep track of additional data on an employee by
employee basis.

Thus, you don't have to keep track of 365 records for each person per year.
HTH

 

[Guest]

Hi

Unfortunately I do need to keep track of all 365 days of the year.
I should of said before, that I work at a bus company. There are no fixed
holidays (apart from Christmas Day when no one works). We operate on 364 days
of the year.

 

[kingston via AccessMonster.com]

You still keep track of all 365 days. You just don't keep track of all 365
days for each person. Since Christmas Day is the only fixed holiday, you
don't need the second table and can simply use the date 12/25. The third
table would be the one where all of the work would be done. It would contain
an employee id field, a date field, and an activity field (vacation, absent,
etc.).

You could have a main form with the calendar year and 364 text boxes if you
really wanted to. Then the user would select an employee and that person's
data would load. The form would accept changes and write it to the table.
What functionality are you looking for; why are you considering moving this
from Excel to Access?

Hi

Unfortunately I do need to keep track of all 365 days of the year.
I should of said before, that I work at a bus company. There are no fixed
holidays (apart from Christmas Day when no one works). We operate on 364 days
of the year.

There are a lot of ways to do this. Here's just one:

[quoted text clipped - 14 lines]

 

[Guest]

It is to use it for reporting really (ie how many people on holiday on a
particular day (or range of days).

I will try the 3 table solution as you have suggested.

The excel version is unmanageable really (with about 300 employees or more),
and we have too many excel spreadsheets causing duplication in certain areas.

You still keep track of all 365 days. You just don't keep track of all 365
days for each person. Since Christmas Day is the only fixed holiday, you
don't need the second table and can simply use the date 12/25. The third
table would be the one where all of the work would be done. It would contain
an employee id field, a date field, and an activity field (vacation, absent,
etc.).

You could have a main form with the calendar year and 364 text boxes if you
really wanted to. Then the user would select an employee and that person's
data would load. The form would accept changes and write it to the table.
What functionality are you looking for; why are you considering moving this
from Excel to Access?

Hi

Unfortunately I do need to keep track of all 365 days of the year.
I should of said before, that I work at a bus company. There are no fixed
holidays (apart from Christmas Day when no one works). We operate on 364 days
of the year.

There are a lot of ways to do this. Here's just one:

[quoted text clipped - 14 lines]

year (ie absent, paid holiday etc).
How could I create a database to do this for each holiday?

 

[kingston via AccessMonster.com]

Those are excellent reasons to port it to to a database. Again, you really
don't need the Holidays table since you only have 1 across-the-board date,
but it might be easier to design it in now in case things change in the
future. Good luck.

It is to use it for reporting really (ie how many people on holiday on a
particular day (or range of days).

I will try the 3 table solution as you have suggested.

The excel version is unmanageable really (with about 300 employees or more),
and we have too many excel spreadsheets causing duplication in certain areas.

You still keep track of all 365 days. You just don't keep track of all 365
days for each person. Since Christmas Day is the only fixed holiday, you

[quoted text clipped - 21 lines]