Hello Kathy,

Some answers get driven by design principles that are good to always
follow, some get driven by (those with) practical experience, but your
particular needs should also drive answers......in the end what's "right" is
what works well for you.

In general, the more thorough/powerful table structures accomodate a wider
range of scenerios in a fully databased fashion(vs. stuffing exceptions into
notes fields etc.) , but they are usually are also more complicated and more
work. Having separate tables for families and individuals is the most
powerful/versatile of the discussed structures (short of/ not counting Allen
Browne's more powerful and abscract structure only briefly mentioned) But
"powerful/versatile" can be a bad idea for a particular situation if it is
overkill.


The one thing I question structurally in your description is a subform for
addresses. This also implies a separate table. IMHO addresses are "one to
one" information for one of the other tables, and thus should probably be in
the table and form with that other entity.

Good luck!

Fred