S
Serendipity
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.
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.