Dave,
You'll need to capture the key value (ex. CustID = a bound field), but
you don't want to capture the ancillary information. (Name, Address, City,
etc...)
You just want to "display" it on the form.
Once you've captured the CustID, you can always re-derive the ancillary
information... in any subsequent form, query, or report.
A popular method is to use a multi-column combo box (ex. cboCustID) to
select the CustID.
Example cboCustID column setup...
CustID CustName CustAddress
142 Jones 12 Main St
cboCustID Combobox properties...
ControlSource = CustID
No of colums = 3
Column Widths = 0"; 1.5"; 2.0"
What this does is... it allows the user to select a CustID by CustName,
the combo displays CustName, but what's really stored in the CustID field in
the table is... the CustID.
Now, given an "unbound" text control, on that form, with a ControlSource
of...
=cboCustID.Column(2)
will always "display" the CustAddress (not capture it, but just display it).
Combo colums are numbered 0, 1, 2, 3, etc..., so column 2 would be the
CustAddress value.
On my website (below) I have a 97 and 2003 sample file called "Combo
populates multiple fields", that shows how this is done.
--
hth
Al Campagna
Microsoft Access MVP
http://home.comcast.net/~cccsolutions/index.html
"Find a job that you love... and you'll never work a day in your life."