Yep, I would have a Persons master table, a PersonStatus table and a
PersonAddress table containing address(es) with a switch to indicate
Active or Inactive status, and follow that along. If a person lives in
Hawaii for the winter and in British Columbia in the summer, both
addresses would be in the PersonAddresses table with one only allowed to
be active at any given time. Saves a lot of keying. You could go as far
as PersonPhones if you really need to, adding a phonetype column to
indicate cell, land, satellite, fax ...
Albert
On 21/02/2012 6:04 PM, William Stacy wrote:
In my efforts to "normalize" my database, I'm even finding the need to
split off postal addresses, telephone numbers, etc into separate
tables. Presently all addresses and phones etc reside in a person
table and/or in a family table. I haven't done this yet, but am
thinking about it. In the end, my "family" table may end up only
having about 3 or 4 columns, which identify the person's mom and dad
for blood relative connections, and maybe a responsible person
(bill-to and family addressee) connections. Can't think of much
else that is needed there.
My reason is this: many people have alternate addresses, some more
than 2 such as office addresses, PO Boxes, military addresses,
vacation homes, bill-to addresses, girl-friend or sugar-daddy
addresses and so on. Same thing is true of phone numbers. Really,
these are almost one-to-many items. In the reverse fashion from what
you might think. Really, a single street address can have many people
associated with it, and the address itself really doesn't change, only
the residents do. Same thing is true of phone numbers. My cell num
is unique, but after I give it up, someone else will eventually get it.
Anyone construct tables thusly?
--
William Stacy, O.D.
Please visit my website by clicking on :
http://www.folsomeye.net
