In TblChurchDateFunctionPeople, make DateFunctionID ChurchDateFunctionID.

Steve

"Steve" wrote in message
...
Hi Scot,

You don't need all those tables! I have assumed there are different
functions for different dates.
TblPeople
PeopleID
FirstName
LastName

TblFunction
FunctionID
Function

TblChurchDateFunction
ChurchDateFunctionID
ChurchDate
FunctionID

TblChurchDateFunctionPeople
ChurchDateFunctionPeopleID
DateFunctionID
PeopleID

Assuming you have TblPeople and TblFunction filled, next create a form on
TblChurchDateFunction and enter all the functions for each church date.
You can use a calendar control for entering the church dates and a
combobox having a rowsource of TblFunction for entering each FunctionID.
Next create a query that includes TblFunction, TblChurchDateFunction and
TblChurchDateFunctionPeople. With the proper design of the query, you will
be able to display a list of each church date and all the functions on
each church date. Use this query as the recordsource of a form and use a
combobox with a rowsource of TblPeople to enter the person for each
function on each church date.

Steve


"Scott_Brasted via AccessMonster.com" u56211@uwe wrote in message
news:a07ff70bde172@uwe...
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

--
Message posted via http://www.accessmonster.com