If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Relational Design
I am designing a relational Family data base which has
among other fields: LNAME & FNAME FOR EACH FAMILY MEMBER, DOB, TASKS (MANY). Should i have seperate tables (linked) for say Husband, Wife & Children as sometimes the LNAME will differ due to defacto etc. If that is the case how do I link say LNAME of Husband to Lname of Wife/Partner. Do I need to call the attribute(field) of the Partner say LNAME of partner in the seperate table or can it also be called simply LNAME (IE DUPLICATED). Same with DOB and Tasks Thanks for any help |
#2
|
|||
|
|||
All the individuals should be in one table, say tblPerson.
Typically, you have another two tables to define the families: one that just holds a record for each family, and a related table that lists the persons in the family and their roles. This tblFamilyPerson table has fields: FamilyID relates to tblFamily.FamilyID PersonID relates to tblPerson.PersonID RoleID relates to a table of roles (e.g. "Husband", "Wife", "Child"). That works, but it has some limitations. For example, if you need to send a mailing to your clients who may be individuals or families, there is no one table you can use. Likewise, if you give counselling sessions to both individuals and families, you cannot set that up. This article suggests a more flexible structu People in households and companies at: http://allenbrowne.com/AppHuman.html It explains how to set up a client table where the client can be an individual or a family. You end up with both in the one table, and then other tables define who belongs to which family and with what roles. Contains example database. -- 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. "Bell" wrote in message ... I am designing a relational Family data base which has among other fields: LNAME & FNAME FOR EACH FAMILY MEMBER, DOB, TASKS (MANY). Should i have seperate tables (linked) for say Husband, Wife & Children as sometimes the LNAME will differ due to defacto etc. If that is the case how do I link say LNAME of Husband to Lname of Wife/Partner. Do I need to call the attribute(field) of the Partner say LNAME of partner in the seperate table or can it also be called simply LNAME (IE DUPLICATED). Same with DOB and Tasks Thanks for any help |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help with design | Ronnie | Database Design | 6 | March 12th, 2005 02:53 PM |
Who owns the copyright on graphic design layouts prepared in MS Wo | Karen | General Discussion | 4 | February 1st, 2005 07:01 AM |
How to assign a menu bar to a report opened in design mode | Gordon | Setting Up & Running Reports | 0 | January 20th, 2005 12:09 AM |
Action queries changing when reopened in design view | Kendra | Running & Setting Up Queries | 2 | August 31st, 2004 12:34 AM |
finding design examples for Invoices and Payments | Paul James | Database Design | 2 | June 9th, 2004 07:14 PM |