Hi Orf,

Your approach is a simple way to handle it, but it misses the benefit of a
relational database. For example, how many children do we provide for?
Should it be 2, 3, 4? What if someone has eight children? Also, it seems
wasteful to make room for a spouse and children when the person is single.
This is the principle behind a relational database - no waste, but the
design is more complex!

The other problem with the single table approach is that it is very
difficult to create other lists, such as members of a committee. If you have
a table of names, all you need is another table that contains the ID entries
for all members of a committee. If there is another committee, just create
another table with the members' ID entries.

Peter
-----------------------------------------------
The NoSpin Group
[log in to unmask]


> -----Original Message-----
> What I would do is have one table using the following fields:
> Title, Initials, First Name, Surname, Address1, address2, Address3,
> City,  State, ZIP, Birthday, TitleW, InitialsW, First NameW, SurnameW,
> BirthdayW, TitleC1, InitialsC1, First NameC1, SurnameC1,
> BirthdayC1, .....

             Do you want to signoff PCSOFT or just change to
                    Digest mode - visit our web site:
                   http://freepctech.com/pcsoft.shtml