Lookup table properties (1 Viewer)

Leo_Polla_Psemata

Registered User.
Local time
Today, 13:03
Joined
Mar 24, 2014
Messages
364
Hi There
I have a field (footbal) in a table (team) , i don't know why it is so hard to tune the lookup properties.


This field, "footbal", looks up values from another table (foot).


Foot table has three fields,

id auto number, primary,

the team name and the

country.



The "footbal" field from team table must look up values from foot table and store the second column.






Here, i would like to store the football name, not the id.
I have tried ALL "bound column" and "Column count" combinations

from properties but i can't convince access to store the name , not the id.

Of cource, IF i remove the id from the lookup table, then it is okay

but i need to have the id as well.
 

Galaxiom

Super Moderator
Staff member
Local time
Tomorrow, 07:03
Joined
Jan 20, 2009
Messages
12,849
You should be storing the ID. Always the ID.

What you display is controlled by the design of the form.
 

Leo_Polla_Psemata

Registered User.
Local time
Today, 13:03
Joined
Mar 24, 2014
Messages
364
You should be storing the ID. Always the ID.

What you display is controlled by the design of the form.


Thanks
Understand your point.

What purpose does the "bound column" serves ?
 

Galaxiom

Super Moderator
Staff member
Local time
Tomorrow, 07:03
Joined
Jan 20, 2009
Messages
12,849
The bound column is the one that is stored in the table from a bound combo or list box. It is the Value Property of the control.

To control what is displayed, increase the ColumnCount and adjust the ColumnWidths. The widths are in cm or inches depending on your regional settings and separated by semicolons. A zero width will hide a column.

Do this in conjunction with RowSource query which will control what fields are available to show.

Only the first non zero width column will display until the the control is dropped down.

The columns are numbered from zero.
 

CJ_London

Super Moderator
Staff member
Local time
Today, 20:03
Joined
Feb 19, 2013
Messages
16,553
you appear to be trying to create a lookup in a table - this is generally a bad idea - you store a number but display text. Use lookups in forms and reports, not tables. Just because you can, doesn't mean you should.
 

Users who are viewing this thread

Top Bottom