If you make a query (qryPersonnel) based on the Personnel table
(tblPersonnel), then make a form with qryPersonnel as its Record Source,
then drag fields from the field list to the form (in design view), can you
see the data?
A typical arrangement with something like WorkHistory is to do what you have
done with the one-to-many relationship, then to use a form/subform to
display the data. To verify that we are talking about the same thing, I
envision a structure something like this:
tblPersonnel
PersonnelID (primary key, or PK)
FirstName
LastName, etc.
tblWorkHistory
HistoryID (PK)
PersonnelID (foreign key, or FK)
StartDate
EndDate
JobTitle, etc.
The relationship is between the two PersonnelID fields. The PK fields are
established in table design view, and the FK field is established by its
relationship to the PK field.
Build a form (frmPersonnel) based on tblPersonnel, and another form
(fsubHistory) based on tblWorkHistory. When you drag, say, FirstName from
the field list onto the form, the text box will be named FirstName (same as
the field). Change it to txtFirstName (or whatever you choose, as long as
it's different from the field name). This will take care of some #Name
problems. You may wish to set the Default View of fsubHistory to
Continuous. Drag the icon for fsubHistory from the database window onto
frmPersonnel. Click the border of fsubHistory, then click View >
Properties. Verify that the Link Child Field and Link Parent Field property
is set to PersonnelID. If it is not, click the three dots; I think the
dialog box will be self-explanatory.
If this works as expected, try substituting qryPersonnel for tblPersonnel as
the RecordSource for frmPersonnel. Does it still work?
This should help get you on the right track, unless I have completely
misunderstood the question.
Now you should be able to enter Personnel information into the main form and
History information (as many separate entries as are needed) into the
subform.