jack drawbridge
jackandpat.d at gmail.com
Thu Mar 17 08:56:17 CDT 2011
I concur with the PostalCode, City, State table set up -- very useful. With respect to the "addresses", will these be shipping address, billing address, physical location address, mailing address, etc... or any combination of same. This could be an issue if these are combined, and you now, or in future need to know which is which. Just a thought... jack On Thu, Mar 17, 2011 at 9:00 AM, Susan Harkins <ssharkins at gmail.com> wrote: > 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? >>> >> > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >