Using Access 2003. I have a school volunteer database. Trying to figure out
the best way to design my tables. The database contains families where the
members have different reasons for being in the database, e.g., student,
parents in various volunteer roles, etc. Do I need a family table which has
only an Id and address information, and then another table for individual
information? I was told that the id in both tables should be autonumber. I
have been using something like SmiMel for the Melvin Smith family so that I
could quickly enter and find records. With hundreds of records in the
database, picking the family from a list before entering data would be
laborious. Please help me know how to proceed.
Do you need to be able to contact/send mailings to anyone, including
student, parent, or family?
If so, download this example and pull it apart:
People in households and companies - Modelling human relationships
at:
http://allenbrowne.com/AppHuman.html
As far as the primary key goes, you can use a text-based key if you wish. It
could get messy for trying to figure out the key to use for families
through.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> Using Access 2003. I have a school volunteer database. Trying to figure
> out
[quoted text clipped - 9 lines]
> database, picking the family from a list before entering data would be
> laborious. Please help me know how to proceed.
Serendipity - 18 May 2007 15:59 GMT
Yes, each individual member might get a mailing, e.g., the for a birthday
party announce, the parents for a volunteer assignment a for sale item. The
link looks right on target. I am digesting it. Thanks.
> Do you need to be able to contact/send mailings to anyone, including
> student, parent, or family?
[quoted text clipped - 21 lines]
> > database, picking the family from a list before entering data would be
> > laborious. Please help me know how to proceed.