S
Scott_Brasted via AccessMonster.com
Greeings,
I am creating a db to track who serves what function in what Sunday at church.
So I think I need 3 tables.
1. people who serve
2. functions they serve
3. dates they serve
Many people can serve many dates and many people can serve many functions on
many dates.
So do I have the three tables and then a join table for people/dates and a
join table for people/function and a join table for dates and functions? And
how do I structure them. I am thinking:
tblPeople
peopleID pk
name
tblFunction
functionID pk
functionName
tblDate
dateID pk
serviceDate
tblJoinPeopleDates
peopleID pk
dateID pk
tblJoinPeopleFunction
peopleID pk
functionID pk
tblJoinFunctionDate
functionID pk
dateID pk
If this structure works, what does the relationship window look like? This is
the first time I have tried anything like this.
Thanks,
Scott
I am creating a db to track who serves what function in what Sunday at church.
So I think I need 3 tables.
1. people who serve
2. functions they serve
3. dates they serve
Many people can serve many dates and many people can serve many functions on
many dates.
So do I have the three tables and then a join table for people/dates and a
join table for people/function and a join table for dates and functions? And
how do I structure them. I am thinking:
tblPeople
peopleID pk
name
tblFunction
functionID pk
functionName
tblDate
dateID pk
serviceDate
tblJoinPeopleDates
peopleID pk
dateID pk
tblJoinPeopleFunction
peopleID pk
functionID pk
tblJoinFunctionDate
functionID pk
dateID pk
If this structure works, what does the relationship window look like? This is
the first time I have tried anything like this.
Thanks,
Scott