One to Many Relationship

[JeRz653]

Hi All,

I have a database that I am building to track customer issues. It currently has 2 tables: tblMembers and tblIssues. Currently, IDNumber is the primary key under the Members table with a one to many to IDNumber in the Issues table.

I'm having trouble comprehending how to solve an issue that may occur. The issue is that there may be situations where a family member of the member may be the inquirer. The ID Number is the same 5 digits for each member of the family. So, obviously, if the wife of the member comes in and we attempt to add a record with her name, it would be a duplicate. Is there a way around this potential issue? I don't have any other information I can really use to differentiate in other relationships within the tables.

I hope I explained it clearly. Please let me know if anything further is needed or if too vague.

Thank you in advance for any assistance!

 

[Ranman256]

EVERY member must have their own ID. Family members can all have the same FamID, but different MemberID.

 

[jdraw]

General model of the tables involved:

Family-->Member-->MemberIssue<---Issue


which means:
A Family has 1 or more Members.
There are many Issues.
A Member may have 0,1 or many Issues.

Good luck.