
Originally Posted by
NTC
as with both IM and J7 comments - I don't quite follow your post when looking at your image. However I think I understand what you are trying to say; whether a combo box or a a lookup field type - there is an issue that it is bound to (and displaying 1 field) but in the real world it is necessary to view the values of other fields in the same record at the same time. To do this you set up unbound text boxes that call/refer to the combo/lookup field's other columns/fields.
First, the underlying query/record set of the combo/look up must include these fields so that when one triggers the drop down action you see all fields during the action of when a record is selected - - then along side the combo/lookup field you put unbound text boxes with the control set to call these other fields using this syntax:
=[ComboBoxControlName].Column(2)
I use column 2 just as an example....in the typical set up default the record set's first field/column is bound and is considered 0, the second field/column is what is displayed in the combo/lookup field and is considered 1; so I used 2 in order to display the field/column......