
Originally Posted by
jzwp11
Welcome to the forum!
First, I would use more descriptive field names in place of the "ID" field in the tables. Additionally, it is best not to have spaces or special characters in your table or field names.
I assume that your contact information table holds the contact info for your employees. Now as to employee wage table, assuming that an employee can have multiple wages (due to raises, promotions etc.) over time and you want to track those changes, then that describes a one-to-many relationship between the employee and the wage table which will be handled like this:
tblEmployees
-pkEmpID primary key, autonumber
-LastName
-FirstName
-Address
tblEmployeeWages
-pkEmpWageID primary key, autonumber
-fkEmpID foreign key relating the wage to the employee in tblEmployees
-dteEffective (effective date of the wage)
-WageRate
You would not need the Days worked (2 weeks) field since you can calculate it from the following table. Assuming that you want to capture the actual work start and end times, an employee will have a start and end date/time for each day worked which describes a one-to-many relationship (one employee to 2 date/times values), and you can calculate the actual time worked from these two records.
You can extract the day of the week from the date using functions in Access.
tblWork
-pkWorkID primary key, autonumber
-fkEmpID foreign key to tblEmployees
-dtetmeWorked (a date/time field that includes both the date and time)
As a note, the foreign key fields indicated above should all be long integer number datatypes to match the autonumber datatype of the corresponding primary key field.