Table Design

G

Guest

Hello there,
Teaching myself access and have some design questions.
I'm trying to design a payroll type database. The pay period closes on the
5th and 20th of each month. The week starts on Monday and ends on Sunday.
Depending on the hours worked we give a $1 bonus on the hour to the employee
but we have 4 categories during a day that an employee can fall into
(dayshift, am parttime, night-weekend and midnight).

So I have 4 tables matching the categories (dayshift, am partime,
night-weekend, and midnight) all with the following fields:
ID (Primary Key)
EmployeeID (Linked to the Employee Table with a one(tblEmployee) to many)
Begin_Date (Linked to the Date table with a one(tblDate) to many
relationship)
Monday_Hours
Tuesday_Hours
Wednesday_Hours
Thursday_Hours
Friday_Hours
Saturday_Hours
Sunday_Hours

The Employees table has the following fields:
AutoNum (AutoNum field)
EmplyeeID (Primary Key)
Last Name
First Name
and so on....

I also have a Date table that has:
AutoNum (AutoNumber field)
WeekBegin (Primary Key)

Is this decent design or is there a better way?
This was all being done in excel but figured I'd give access a go at it and
just want to make sure I'm working with good design.
Thank you,
x01kgb
 
G

Guest

One thing I would suggest would be to combine your 4 category tables. These
are redundant. Simply add a Category table, and a CategoryID in the primary
table.

Sharkbyte
 
G

Guest

Sharkbyte said:
One thing I would suggest would be to combine your 4 category tables. These
are redundant. Simply add a Category table, and a CategoryID in the primary
table.

Sharkbyte

Well... that makes perfect sense.
That should've been obvious in hindsight...
Thanks Sharkbyte!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top