I am working on a db for a wedding. I have a family table and another for individual family members. A member may me invited to 1 or more parties. Some will be for couples. I may be brain dead but all I can think of is a y/n box for each separate event on the guest table. Suggestions? Good luck and may God bless.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Sub list for shower invitations 1
- Thread starter JMANER
- Start date
-
1
- #2
You have a many-to-many relationship there. A family member may be invited to multiple parties, and a party hosts multiple family members.
Usually, the best way to implement a many-to-many relationship is to create a table that contains a foreign key for each of the tables in the relationship. In this case, your Invitations table would have the key of the Party table and the key of the Family Member table. The composite of these two keys is the key of your Invitations table. You may want additional columns in it--say, for a meal choice or an RSVP response, which depends on both the party and the family member--but often you won't need any additional columns.
To use the many-to-many table (often called a "join table"
, you typically build a query that includes all three tables, with the join table connected by lines to the keys of the other two tables. You can then filter by family member to see the parties to which he/she is invited, or filter by party to see which family members are invited. Rick Sprague
Usually, the best way to implement a many-to-many relationship is to create a table that contains a foreign key for each of the tables in the relationship. In this case, your Invitations table would have the key of the Party table and the key of the Family Member table. The composite of these two keys is the key of your Invitations table. You may want additional columns in it--say, for a meal choice or an RSVP response, which depends on both the party and the family member--but often you won't need any additional columns.
To use the many-to-many table (often called a "join table"
, you typically build a query that includes all three tables, with the join table connected by lines to the keys of the other two tables. You can then filter by family member to see the parties to which he/she is invited, or filter by party to see which family members are invited. Rick Sprague- Status
