Design question
From: disturbedOne <gmusher_at_gmail.com>
Date: 2 Aug 2006 14:46:08 -0700
Message-ID: <1154555168.534596.120300_at_h48g2000cwc.googlegroups.com>
Hi all, not sure this is right group. Hoping someone could give me so advice on my database design.
Date: 2 Aug 2006 14:46:08 -0700
Message-ID: <1154555168.534596.120300_at_h48g2000cwc.googlegroups.com>
Hi all, not sure this is right group. Hoping someone could give me so advice on my database design.
What is the best way to join these tables
Short version goes like this....
I have tables : Person or Employee, Dependent (person is fk in dep table) then I have a bunch of tables related to insurance policies/events
what is the best way to join these two together given this scenario
A person can be an insured with many covered dependents on one policy A person can be insured with one or more policies A dependent can be the only insured policy holder but we must know what employee this relates back to.
I was thinking an insured persons table with person id and dependent id - but this bothers me for some reason....any suggestions?
Hope this was clear....
Thanks in advance for your time!
Received on Wed Aug 02 2006 - 23:46:08 CEST