Re: HOWTO: company & client addresses 1 or 2 tables?

"Niels van der Kam" <n.a.van.der.kam_at_home.nl> wrote in message news:<bc40ok$c4k$1_at_news4.tilbu1.nb.home.nl>...
> I took a look at the Traffic Cop example. Almost the same...but only one
> address per cop / violator. I need the possibility for multiple.
Here is a Data Model for Customers and Deliveries that might help :- http://www.databaseanswers.com/data_models/customer_deliveries/index.htm

It shows that a Customer can have many Addresses - Billing, Delivery, Residential and so on.

Thanks for the kind words about my site and I'm glad that you find it helpful.

Regards

Barry

> "Barry" <barryw_at_databaseanswers.com> schreef in bericht
> news:55816d8a.0306091430.3d6712e1_at_posting.google.com...
> > "Niels van der Kam" <n.a.van.der.kam_at_home.nl> wrote in message
> news:<bc2j6t$ttg$1_at_news2.tilbu1.nb.home.nl>...
> > > Or should I make two tables one for company addresses and one for client
> > > addresses?
> > > Are there rules for this kind of situations?
> > I guess the rule would say 'Identify the Things that occur naturally
> > and model them accordingly'.
> > In this case, the Things are Addresses and so you should have just one
> > Address Entity with a foreign address_id key in the company and client
> > tables.
> > Here's an example on my Database Answers web site of a Data Model for
> > Traffic Cops showing Violaters who have Addresses, (just like Cops).
> >
> > Barry Williams
> > Principal Consultant
> > Database Answers
Received on Fri Jun 13 2003 - 21:42:16 CEST