Let's see if I get this straight:
Location::__pk_LocationID = Personnel::_fk_LocationID
You are on a layout based on location and you want to create a new personnel record and link it to the current location record?
Seems backwards as you would normally create a new record on the personnel layout and select a value in _fk_LocationID to link it to a specfiied location. This could be done, however, with a script.
Sorry, reading it it does sound backwards to me, too. Let me be more clear,
I am in a layout based on the Personnel table and want to "import" the information from the Location table.
Sorry about the confusion,
Ok, that's simpler to do.
Do not put the primary key field from location on the layout.
Instead, format the foreignkey field as a drop down list or pop up menu. Define the value list to list the Primary key values from Location in Field 1 and a name field from location in field 2. (Sometimes you have to define a calculation field for field 2 that combines data from several fields.)
When you select a location by name from this field, the value list enters the matching primary key value and links it to your personnel record. If you place other fields from Location on this layout, they will then display data from the selected location once you have selected a location from the value list. (You can hide the primary key in the value list by clicking "show only values from second field", but if you make this selection, you should also make sure that whatever field you use in field 2 stores only unique values or duplicates in this field will omit the second instance of the same name.)
This approach with the two column value list is the simplest way to set this up. It's not the only option. As the number of values in the value list increase, either a conditional value list or a script enhanced value selection method often becomes necessary to keep from scrolling through very long lists of values.
Excellent! This has been driving me nuts for days...