TblEmployee
EmployeeID
EmployeeFirstName
EmployeeLastName
<Other fields about an employee>
TblWorkLocation
WorkLocationID
WorkLocation
TblWorkType
WorkTypeID
WorkType
TblEmployeeWork
EmployeeWorkID
EmployeeID
WorkDate
TblEmployeeWorkDetail
EmployeeWorkDetailID
EmployeeWorkID
WorkLocationID
WorkTypeID
WorkStartTime
WorkFinishTime
If there is a distinct set of worked performed such as Check Reads and
Collections, they would be your data in the WorkType field of TblWorkType.
Then as you enter employee work, you would have a combobox that gets its
items from TblWorkType.
Note I added a new table for location. If there is a distinct set of work
locations such as Judy System and Cedargrove System, they would be your data
in the WorkLocation field of TblWorkLocation. Then as you enter employee
work, you would have a combobox that gets its items from TblWorkLocation.
Note I added the table TblEmployeeWorkDetail. This table records one or more
jobs done by a specific employee identified by EmployeeID in TblEmployeeWork
on a specific date identified by WorkDate in TblEmployeeWork.
TblEmployeeWork and TblEmployeeWorkDetail are related through
EmployeeWorkID.
EmployeeWorkID is the primary key of TblEmployeeWork and a foreign key in
TblEmployeeWorkDetail. You would enter employee work records in these two
tables in a main form based on TblEmployeeWork and a subform based on
TblEmployeeWorkDetail.
The above table structure assumes that on any day an employee may work at
more than one location. If that is not the case an an employee will ALWAYS
work at the same location albeit possibly more than one job type, the
WorkLocationID should be moved from TblEmployeeWorkDetail to
TblEmployeeWork.
Steve
(e-mail address removed)