Defining Primary Key to use relationships

[SeniorsSummerStudent]

This should be something easy to do, but I'm running into trouble. I have one
"Master List" (table) of data. These are the names and addresses of
individuals. These individuals also belong to a Christmas list, a Volunteers
list, or a Provincial list, sometimes all three!

Is there a way I can set things up so that a change to the 'master list'
will also change the same address on the other lists?

EX: I have John Doe on my Master List at 123 Anystreet. He is also on
Christmas list. Can I link Master and Christmas list in some way so that a
change on Master will also change the address on the Christmas list?

 

[Allen Browne]

Use 3 tables:

Person table (one record for each person):
PersonID AutoNumber primary key
Surname
FirstName
Address
City
...

MailList table (one record for each type of mailing list):
MailListID AutoNumber primary key
MailList Text name of this list.

MaillistPerson table (one record for each combination):
MailListID Number Foreign key to MailList.MailListID
PersonID Number Foreign key to Person.PersonID

So, if John Doe is on mailing list "Christmas" and also mailing list
"Volunteer", he will have 2 records in table #3.

This means there is only *one* place to maintain the person's name and
address, and it is very quick and easy to put the person onto another list
as well.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

"SeniorsSummerStudent" <[email protected]>
wrote in message
news:[email protected]...