Path: news.easynews.com!core-easynews!newsfeed1.easynews.com!easynews.com!easynews!newspeer1.nwr.nac.net!news.maxwell.syr.edu!sn-xit-03!sn-xit-06!sn-xit-09!supernews.com!postnews1.google.com!not-for-mail From: barryw@databaseanswers.com (Barry) Newsgroups: comp.databases.theory Subject: Re: HOWTO: company & client addresses 1 or 2 tables? Date: 9 Jun 2003 15:30:13 -0700 Organization: http://groups.google.com/ Lines: 15 Message-ID: <55816d8a.0306091430.3d6712e1@posting.google.com> References: NNTP-Posting-Host: 195.93.34.12 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1055197814 4592 127.0.0.1 (9 Jun 2003 22:30:14 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 9 Jun 2003 22:30:14 GMT Xref: core-easynews comp.databases.theory:26754 X-Received-Date: Mon, 09 Jun 2003 15:29:31 MST (news.easynews.com) "Niels van der Kam" wrote in message news:... > 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