DLookup

thanks!

Yes this has been an issue for me and the topic of several fruitful exchanges with Rich.

Basically, your choices seem limited to utilizing DLookup (which can be slow if multiple TextBoxes are so populated, but usually an easy solution) or creating a query from the bound table which replaces its numeric, foreign key-fields items with string data obtained via tables linked to these keys in the query.

DLookup is my goto choice. After all, generally, when populating a Form's TextBoxes, a slight time lag in completing all fields is of little consequence, and as system hardware gains in operating speed, has become virtually imperceptible.

However, either of these two methods renders the Form's "encoded" TextBoxes incapable of receiving new data -- a need sometimes arising after a Form has fully resolved all fields. I've made elaborate subForm solutions but have basically concluded that the simplest solution is an "edit" CommandButton which opens a Form specifically constructed to supply the original table with the desired key-field alteration. Sometimes, then, I need to REQUERY when returning to the display Form.

At this stage, I don't think there's a set standard, but this is an opportunity to create your most efficient, economical and effective programming solution suited to your situation. Others may have their own preference.

If you are only displaying one employee you may also be able to use the Forms!FormName!FieldName notation in your subform.
Remember they are technically two forms even though one is inside of the other.

Check out the Value From a Form and Value From Subform videos for more info on getting the value.  This way you would not need a DLookup if it is the same employee as in the parent form.

thanks much for all of these options... definitely appreciate the feedback :)