Re: Relation problem

Because I need to keep a single table of address with no duplicates. We have regurlar updates for address validations, new addresses and so on.

Michel

Jan Hidders <hidders_at_REMOVE.THIS.win.tue.nl> wrote in message news:946blu$hkt$1_at_news.tue.nl...
> Michel wrote:
> > Designing this large database where we store adresses as their own
> > entity. i.e. an address exist by itself. We also have individuals AND
> > organizations that can have have more than 1 address. So far so
> > good, created a link table were I wanted to use the primary key as
> > individualID and AddressID.
> >
> > This would be great, but it's got to be an individual OR an
> > organization, so I cant have referencial integrity enforced at the
> > database level.
>
> Why not simply split the table Addresses in OrganizationAddresses and
> IndividualAddresses? You can always define a view that takes the union
> of these two tables if you need it.
>
> --
> Jan Hidders
Received on Thu Jan 18 2001 - 16:41:33 CET