If a field in MS-Access, has a lookup defined which is a combo-box which uses a Value List... Is it possible to obtain the list of available choices for that field programatically?
The list has to be stored somewhere... but I don't see anyway to access it. I thought maybe it could be accessed through the TableDef object but that doesn't apear to be there.
The reason, I want to have access to the value list is to output BOTH the numeric value (stored in the table) and the text assigned to that value from the value list...
So if the Value List is defined something like...
1;Item One; 2;Item Two; 3;Item Three
I would like to be able to output a query result that includes both the number and the text...
1 Item One
3 Item Three
1 Item One
5 (item not found in Value List)
2 Item Two
... etc.
Please save replies about proper database design and using related tables for defining lookup values instead of using this lookup/combobox feature in the table design. I already know thats how it should have been designed. I am just trying to utilize this database structure that someone else designed 10 years ago. The situation doesn't warrant re-design of the existing data model.
The list has to be stored somewhere... but I don't see anyway to access it. I thought maybe it could be accessed through the TableDef object but that doesn't apear to be there.
The reason, I want to have access to the value list is to output BOTH the numeric value (stored in the table) and the text assigned to that value from the value list...
So if the Value List is defined something like...
1;Item One; 2;Item Two; 3;Item Three
I would like to be able to output a query result that includes both the number and the text...
1 Item One
3 Item Three
1 Item One
5 (item not found in Value List)
2 Item Two
... etc.
Please save replies about proper database design and using related tables for defining lookup values instead of using this lookup/combobox feature in the table design. I already know thats how it should have been designed. I am just trying to utilize this database structure that someone else designed 10 years ago. The situation doesn't warrant re-design of the existing data model.