Gold standard for database design: as in the case of the extended family member. Is the gold standard to have one table for contact list and then have fields for identifying/classifying others i.e. customer vs employee, parent vs child? If you have one table with classification of customer versus employees and then you develop family members, would you put the family in the same table and how do you relate them to someone else in the same table and classify them. Are you not creating a circular reference?
Adam Schwanz
@Reply 5 years ago
Tables that store the same information should be grouped together generally. In this case "People", it could be employees, customers, children or whatever you want, if you store the same information for all of them, it's easier to put them together in a table and then add fields to identify what they are. If you are not storing the same information and you don't really care about the childs information, you just want to link the child to the parent, you could make another table with a one to many relationship if you want.
Scott Axton
@Reply 5 years ago
Check out the Self Join Relationships video. That might help clarify some of your questions.
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Access Expert 4.
