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
|
|||
|
|||
Avoiding Duplicates
I am building a database with family information including social security
numbers for family members. I want to avoid including someone in more than one family by not allowing a duplicate ssn. I'm not sure how to go about doing this since there are several fields with ssn's for each family member. Any suggestions? -- Just Learning |
#2
|
|||
|
|||
Avoiding Duplicates
On Wed, 22 Oct 2008 20:20:01 -0700, LindaH
wrote: I am building a database with family information including social security numbers for family members. I want to avoid including someone in more than one family by not allowing a duplicate ssn. I'm not sure how to go about doing this since there are several fields with ssn's for each family member. Any suggestions? Normalize your incorrect database structure. The SSN (if it should be in your table AT ALL, it may violate some privacy laws) should exist only once, in one People table. Each person, regardless of how that person is related to other people, should have their own record. Perhaps you could post a description of your table structure; it's quite possible that someone could suggest a better table design. -- John W. Vinson [MVP] |
Thread Tools | |
Display Modes | |
|
|