I have two tables at the moment, the main officers table has Regimental
number ( Primary Key) Surname, First Name.
The second table has training completed including Regimental (primary key)
Surname, course completed whch is a dropdown box, completed date and review
date.
I would recommend NOT using "Lookup Fields" in your Tables. See
http://www.mvps.org/access/lookupfields.htm for a critique. They're not
necessary (ever) and can be really confusing.
Are you saying i should delete the regimental and name from all tables exept
the initial officers details and this will self populate the correct name on
the all forms when a regimental is entered?
The other tables should contain only the regimental number (as a foreign key,
a link to the officers table). You can *DISPLAY* the name on any other form by
using a combo box bound to the regimental number (let's call it cboOfficer);
you might base this combo on a query such as
SELECT RegNo, [Surname] & ", " & [First Name] AS Fullname FROM Officers ORDER
BY Surname, [First Name];
This will show (e.g.)
32267 Aarons, Michael
31558 Barnes, Sarah
22601 Carrons, Bob
in the combo, and store the regimental ID in the table.
In a separate textbox on the form you can display the name by using a control
source
=cboOfficer.Column(1)
The Column property is zero based so it will display the second column
(Fullname) from the selected record of the query.