[AccessD] DB Design Question - too much normalization?

That was my question -- 3 tables of addresses?
A Zip code lookup table can be a cool feature if someone's going to be 
entering lots of addresses and repeat Zip codes.

Susan H.



> Rocky,
> Just curious, but why 3 tables?
> jack
>
> On Thu, Mar 17, 2011 at 12:16 AM, Rocky Smolin 
> <rockysmolin at bchacc.com>wrote:
>
>> 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?