Your HoursWorked table needs a new unique index on the Date and EmployeeID fields. Find the index button for the table in design view, create a name, add the fields, set the Unique property to 'Yes'.
The impact of this is that the table will not allow the duplicate entry.
Cheers,
Thread: relational database design - timesheet  |
|||||||||||||
|
Started 1 month, 1 week ago by JimSmith
Hi,
I can't get my head around this very basic relationship between tables, and was hoping for some guidance.
I want to store the number of hours worked by each named person on each date. Many individuals can work on the same date. However I want to set up the relationships in the access database to ensure it is impossible to record more than number of hours worked per date per person....
|
|
||||||||||||
|
|||||||||||||
Other posts in this thread:
lagbolt replied 1 month, 1 week ago
Size: 297 bytes
Customize: 
JimSmith replied 1 month, 1 week ago
Many thanks for your assitance, and such a quick reply. That entirely solves my problem.
Thanks again!
Size: 117 bytes
Customize:
|
Top contributing authorsRelated threads on "Access World Forums":Related threads on other sites: |
||||||||||||
Thread profile page for "relational database design - timesheet" on http://www.access-programmers.co.uk.
This report page is a snippet summary view from a single thread "relational database design - timesheet", located on the Message Board at http://www.access-programmers.co.uk.
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity
Home |
About Us |
Submit Your Site |
Update Your Site |
Get Search For Your Site |
Partners |
Contact |
Search Plugin |
Blog |
 |
Last Searches | Top Searches |
Designated brands and trademarks are property of their respective owners.
Use of this website constitutes acceptance of BoardReader's User Agreement and Privacy Policy.