Two table database input problems

[Guest]

I am creating a db to copy the information from a job application form. There
are two tables in this db. The first table contains a unique identifier that
is an auto generated number and will be assigned to the job application. The
second table has as its primary key the persons soc sec number. Table two
will contain the persons ssn, name, address, city, state, zip, and phone
number. The first table contains all of the applicants other information,
where went to school, work history, which position they are applying for,
etc. These two tables will not import any information from any other db that
the company has. IF the person is hired they will then be put into a
different db. The purpose of the db I am creating is to track the progress of
the person through the hiring process.

Here is the problem I am having. I am trying to find out if it is possible
to create a single form that will put the information into both tables rather
than having to enter information into two tables separately. I would like the
form to reflect the flow that exists on the job application to make keying in
data more easy for the end user. The relationship between the tables is one
to many.

When I created the form using the wizard it will only put information into
the table that is using the ssn as the primary key only. When I attempt to
type information into the fields from the other table nothing is entered at
all, the fields remain blank on the form. Any ideas as to what I am doing
wrong?

When I created a form using the wizard

 

[Guest]

I failed to include that the persons ssn will be a foreign key in the first
table. The second table is linked to the first via the persons ssn.

 

[tina]

standard form setup to display a 1:n relationship between two tables, is a
mainform/subform. main form bound to parent table ("one" side), subform
bound to child table ("many" side). as long as you set the subform control's
LinkMasterFields and LinkChildFields properties to the name of the primary
key/foreign key fields, records in the subform will be automatically linked
to the parent form record at the time of data entry.

btw, suggest you reconsider using the SSN as primary key. unfortunately,
though each person's SSN *should be* unique, in reality there are a lot of
duplicate SSNs floating around out there (think identity theft).

hth

 

[Guest]

I have since found out that I need to make one table a subform. This cleared
up my problems.