Working hours database: I'm going mad...

The database I am using now has a 1:m relationship. Employee info is in the
main form and the records are in the subform. I know that for each employee,
dates are being repeated.

This database needs to be improved upon and how the date information is
incorporated in to the design is major headache!

The major problem I have is that I am not entirely sure how I want users to
enter the information since there are so many variations (or is that the
point? LoL)

I haven't included all the fields for each table but here are the
relationships them.

tble_Dept
DeptID (PK)

tble_Subdept
DeptID (FK)
SubdeptID (PK)

tble_employee
SubdeptID (FK)
EmployeeID (PK)

tble_holiday (will be used as a holiday booking form)
EmployeeID (FK)

tble_week
EmployeeID (FK)
WeekID (PK)
Date
Rate

tble_record
RecordID (PK)
SubdeptID (FK)
WeekID (FK)

tble_absence (used for recording absences)
RecordID (FK)

In the above design I have "tble_week" as a link between the employee and
the record but is this necessarily the best thing ???? dates are going to be
repeated for each employee.

I could have the date as a main table so I can have all 52 weeks of the year
(2007)

Before anyone asks, a major component of this database is that I want to
record the department and subdepartment each employee is affiliated to, even
though an employee can work in any subdepartment. This is important in terms
of how the business is operating.

Are any problems raised by this design?

Hi Scuba

I suggest you repost with a more specific question. What you have said here
is analogous with "I've painted a picture, but is it art?" :-)

What do you actually want to achieve? What is the problem?
--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand

"scubadiver" wrote in message
...
The database I am using now has a 1:m relationship. Employee info is in
the
main form and the records are in the subform. I know that for each
employee,
dates are being repeated.

This database needs to be improved upon and how the date information is
incorporated in to the design is major headache!

The major problem I have is that I am not entirely sure how I want users
to
enter the information since there are so many variations (or is that the
point? LoL)

I haven't included all the fields for each table but here are the
relationships them.

tble_Dept
DeptID (PK)

tble_Subdept
DeptID (FK)
SubdeptID (PK)

tble_employee
SubdeptID (FK)
EmployeeID (PK)

tble_holiday (will be used as a holiday booking form)
EmployeeID (FK)

tble_week
EmployeeID (FK)
WeekID (PK)
Date
Rate

tble_record
RecordID (PK)
SubdeptID (FK)
WeekID (FK)

tble_absence (used for recording absences)
RecordID (FK)

In the above design I have "tble_week" as a link between the employee and
the record but is this necessarily the best thing ???? dates are going to
be
repeated for each employee.

I could have the date as a main table so I can have all 52 weeks of the
year
(2007)

Before anyone asks, a major component of this database is that I want to
record the department and subdepartment each employee is affiliated to,
even
though an employee can work in any subdepartment. This is important in
terms
of how the business is operating.

Are any problems raised by this design?