Lookup results problem...

  • Thread starter Thread starter Tahl G.
  • Start date Start date
T

Tahl G.

I am trying to build a lookup. I have two tables. The
first table contains 5 text fields that are the source for
my lookup. The second table contains the field where I
want the lookup results to appear. When I use the wizard,
I end up with a 1 row x 5 column object in the pull down.
What I would like is a pull down where I can select the
text from 1 of the 5 fields. Can this be done?
 
I am trying to build a lookup. I have two tables. The
first table contains 5 text fields that are the source for
my lookup. The second table contains the field where I
want the lookup results to appear. When I use the wizard,
I end up with a 1 row x 5 column object in the pull down.
What I would like is a pull down where I can select the
text from 1 of the 5 fields. Can this be done?
Click to expand...

Well... the real question is SHOULD it be done. I'd say no. As far as
that goes, I'm a longstanding foe of ever using the "Lookup" field
type AT ALL - see

http://www.mvps.org/access/lookupfields.htm

for a critique.

Each field in a table should contain one distinct atomic attribute of
the Table's Entity. If you have a choice of five fields into which to
store the same kind of data, your table is not properly normalized!

Could you describe the two tables, and what they contain, and what
you're trying to accomplish?
 
This is a contact/sales management db. My first table contains 5 fields [among other things]. Each of those fields represents the name of a contact at the same client. My second table is to log calls. When I create a new call, I want to be able to use a pull-down to select the name of the person I am calling from Company "X".
Click to expand...

Your first table is incorrectly structured, then. You have a one
(client) to many (contact) relationship - rather than having all the
contects in different fields in one record, you should have a separate
Contacts table related one-to-many to the Clients table, with one
RECORD per contact. Someday you'll need six contacts... in addition to
the fact that the "wide-flat" structure makes what you request
difficult or impossible.

The Calls table should be related one-to-many to the Contacts table,
and should contain the ContactID (and only the ID, not the name). This
can be done very easily using a Form with a combo box; it is not good
practice to use table datasheets for data entry or display.
 
Back
Top