Re: Normalization: Tables for Addresses?
- From: "Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx>
- Date: Tue, 21 Nov 2006 19:41:03 -0500
In addition to all the advice you've already received, take a look at
http://www.databaseanswers.org/data_models/customers_and_addresses/index.htm
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
"Peter Stone" <PeterStone@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:750288DD-DE70-448E-AFCF-0AB13055B279@xxxxxxxxxxxxxxxx
Novice/WinXP/Access 2003
Good Evening
With good advice from this forum, I have a normalized db with one-to-ones,
one-to-manys, and many-to-manys.
But, how do I normalize addresses. Northwind db doesn't help because they
give everyone a one-line street address and one phone number.
Each address is attached to an organization.
I presume:
tblStreetAddresses (with each line of the address in a separate record).
tblPostCodes (with PostCode as ID and fields for IDCity and Suburb).
tblTelephones (with fields Telephone and TelephoneType).
tblEmails
tblCities
Sometimes people share the same address and telephone numbers.
Will there be problems if one line of the address is the same as a
different
address?
Do I allow duplicates in the address field? There could be a 22 Rose
Street
in different suburbs.
Room 15
22 Rose Street
Any Suburb
Room 99
22 Rose Street
Any Suburb
22 Rose Street
Some Other Suburb
Or should the StreetAddress be in one field with lines separated by
commas?
Should the street number be in a separate field?
On the Net, I saw advice to put words like Street and Avenue in a separate
table...surely that's not necessary.
Thanks
Peter
.
- Prev by Date: Re: After splitting
- Next by Date: Re: After splitting
- Previous by thread: Re: Normalization: Tables for Addresses?
- Next by thread: Re: Use a variable number of fields
- Index(es):
Relevant Pages
|