[AccessD] DB Design Question - too much normalization?

_______________________________________________________________________________________

Note: This e-mail is subject to the disclaimer contained at the bottom of this message.
_______________________________________________________________________________________



I usually have a seperate table for State and then a table for Postcodes with the state linked as a FK.  Then I tie the Postcode table to the address (which has PCode and State together).

Regards
Darryl.


________________________________________
From: accessd-bounces at databaseadvisors.com [accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin [rockysmolin at bchacc.com]
Sent: Thursday, 17 March 2011 3:16 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] DB Design Question - too much normalization?

Dear List:

I'm putting together an app for a client that will have three tables that
will have address information.  There will probably be no overlap.

Normally I would put address, city, state, zip, main phone, main fax, etc.,
fields into each table.

Is there any reason to make an "address" table with an autonumber PK and an
FK to the address table in each of the other three tables?



MTIA


Rocky Smolin

Beach Access Software

858-259-4334

Skype: rocky.smolin

www.e-z-mrp.com <http://www.e-z-mrp.com/>

www.bchacc.com <http://www.bchacc.com/>





--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________________________________________________

The information transmitted in this message and its attachments (if any) is intended 
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in reliance 
upon this information, by persons or entities other than the intended recipient is 
prohibited.

If you have received this in error, please contact the sender and delete this e-mail 
and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or distribute 
the information contained in this e-mail and any attached files, with the permission 
of the sender.

This message has been scanned for viruses.
_______________________________________________________________________________________