one user, multiple records
- Thread starter kivenage
- Start date
R
Rich
Guest
You have a One to Many relationship between Staff and Jobs, you need the relevant Tables and Form/subform structures to reflect this
- Local time
- Yesterday, 22:13
- Joined
- Feb 28, 2001
- Messages
- 30,567
When you describe this problem and then use "Datasheet" you are revealing an Excel mindset, perhaps.
What you have described is a classic three-table situation, one table for the person and another for the job, plus a linking table that has one entry for each job each person holds.
The HeldJob table has the person ID and the Job ID (and if the situation is simple enough, nothing else.)
Now, if each job is unique, you could GET BY with two tables, putting the person's ID in the JOB table. But if the same job can be held by two people at the same time, then you need the third table. Like, suppose you had job slots for TWO mechanics with the same exact job descriptions. You could have two mechanics at the same time. In this case, the third table becomes absolutely mandatory.
What you have described is a classic three-table situation, one table for the person and another for the job, plus a linking table that has one entry for each job each person holds.
The HeldJob table has the person ID and the Job ID (and if the situation is simple enough, nothing else.)
Now, if each job is unique, you could GET BY with two tables, putting the person's ID in the JOB table. But if the same job can be held by two people at the same time, then you need the third table. Like, suppose you had job slots for TWO mechanics with the same exact job descriptions. You could have two mechanics at the same time. In this case, the third table becomes absolutely mandatory.
