MajP
You've got your good things, and you've got mine.
- Local time
- Today, 11:08
- Joined
- May 21, 2018
- Messages
- 9,480
Again if you explain this we can help. Here is a quick normalization.
Lets say I have Project, a project has several workgroups working on it, and each group has several members.
So if the first Project ID is 1 and Workgroups 7 and 9 are related to project 1 then the ProjectID_FK for 7 and 9 is 1. In a query you can link the two together.
If a person can only be related to a single workgroup then
Now my guess is that is buisness wise unrealistic. People probably are involved in several workgroups to do that you need a junction table to create a many to many. You would remove the workGroupID_FK from the above table and create a junction table.
in this table you would have values like
This then shows that person 34 is related to project 1 and project 2.
Lets say I have Project, a project has several workgroups working on it, and each group has several members.
Code:
tblProject
ProjectID_PK 'normally an autonumber primary key
ProjectName
.... only fields unique to a project
Code:
tblWorkGroups
WorkgroupID_PK ' normally an autonumber PK
WorkGroupName
WorkGroupDescription
..... other fields only unique to a workgroup
ProjectID_FK 'this is a foreign key relating a workgroup to a project.
If a person can only be related to a single workgroup then
Code:
tblPersons
PersonID_PK ' primary key usually autonumber
PersonFirstName
PersonLastName
... other person unique fields
WorkgGroupID_FK ' a foreign key to the workgroup
Code:
tblWorkGroup_Members
WorkgroupID_FK
MemberID_FK
Code:
1 22
1 34
1 245
2 2
2 11
2 34