Leo_Polla_Psemata
Registered User.
- Local time
- Yesterday, 20:06
- 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.
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.