No wonder you don't want to change it. You went to a lot of trouble putting
together all of those tables.
Here'a a pretty concise way of looking at tables: A table should contain
information about a single real-world entity (application, child, etc.).
You should be able to describe its purpose in a single sentence without
using the word "and". Having said that, you can have first name and last
name, or name and address, and things like that in the same table. Items
such as FirstName, LastName, Street, City, Zip, Phone and so forth are all
parts of a person's contact information, so they could all be in the same
record in the People table (or whatever you would like to call it). A main
reason for related tables is to avoid duplicating information. Consider
Social Security numbers. That number identifies you for tax and benefits
purposes, no matter if your name and address changes. If your name and
address were part of the record for every tax or benefit transaction, then
old records would contain information that may no longer be current.
There is no real reason to have a separate address table. In most cases you
will want that information in each person's record. If two people are at
the same address and one of them moves, what would you do if you had linked
both to the same address record? However, you may choose to have a Parent
table with name and address information. Children would be in a related
table, but the address would appear only once (in the Parent table).
The whole issue of parents and children can get a bit murky, since children
grow up and may become parents themselves. In that case, and in other cases
as well, you may choose to put all people into one table, and to use check
boxes or some such to separate them into categories. I will ignore that,
since it sounds as if you aren't dealing with that situation.
What I said about addresses applies to phone numbers and other personal
information.
Could the same person be an Applicant more than once? If so, you need to
store Applicant information in its own table. In that case you would have
an Application table, an Applicant table, and a Child table.
tblApplication
ApplicationID (PK)
AppDate
Reason, comments, and other information about that specific application
tblApplicant
ApplicantID (PK)
ApplicationID (FK)
AppFirstName
other personal information
tblChild
ChildID (PK)
ApplicantID (FK)
ChFirstName and other information specific to the child
Create relationships between the PK fields and their namesake FK fields.
Click Enforce Referential Integrity for all.
Build an Application form, and subforms for Applicant and Children as I
described. Don't worry about data for now. Just create the tables and
forms, insert the subforms as described, and try adding a few sample
records. Get used to how this can work.
For handling the questions, see my remarks in the previous post. For now,
don't worrry about that. Make some related records, and get that part of it
working.
If there is a reason you cannot change your design, about all I can suggest
is to see Help for information about one-to-one relationships. Apply that
relationship between the address table and the People table, etc., and get
ready for an administrative nightmare.