>>>I am trying to normalize a data model in an insurance module I am working on. Here's the deal: Everything pretty much centers around the "claims" table, because you file a claim to get paid from the insurance company. If a "claim" is filed, it requires an "insured", so I have an "insured" table. Here's where I'm trying to normalize, maybe I need a different structure, who knows? If there is an "insured", there is definitely going to be a custome, so I need a "customer" table. This "customer" table has a lot of the same data that the "insured" does. In most cases, the "insured" is the "customer". Claims require both an "insured" and a "customer". The only difference between the "customer" and the "insured" is that the "insured" table will hold alot of particular info on insurance. One other thing I might mention is that not every "customer" will have a claim filed, because some customers don't have insurance. Thanks for any help.
>>
>>
>>
>>So... Whats the question? (s)
>>
>>Tom
>I am trying to normalize the tables, customers, and insured. They would have lots of redundant data because often they are the same person. But I can't merge the two tables because the insured may not be a customer. The question is: How do I normalize the data model in this aspect?


I thought I saw a pretty good answer to that (reply). Were you happy with it?

Tom