If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Combo Boxes/Queries
When I create a query based on a table, where I used combo boxes, the field
comes up with a number? Should you have the field as a Lookup field in the table or create a combo box in a form as a lookup or SQL? Thanks. -- Denise B. |
#2
|
|||
|
|||
Combo Boxes/Queries
Denise
Congratulations! You've (re-)discovered one of the reasons folks here in the newsgroups hold the "lookup field" data type in table definitions in general low regard. What is actually being stored in your table is what you are finding, the primary key of the record in the lookup table. ... even though looking in the table makes it look like the table's storing the "looked up" value! Most folks here strongly recommend changing the lookup field in the table back to a number field (depends on the PK type in your lookup table), then using a combobox based on the lookup table in a form. Good luck! Regards Jeff Boyce Microsoft Access MVP -- Disclaimer: This author may have received products and services mentioned in this post. Mention and/or description of a product or service herein does not constitute endorsement thereof. Any code or pseudocode included in this post is offered "as is", with no guarantee as to suitability. You can thank the FTC of the USA for making this disclaimer possible/necessary. "Denise" wrote in message ... When I create a query based on a table, where I used combo boxes, the field comes up with a number? Should you have the field as a Lookup field in the table or create a combo box in a form as a lookup or SQL? Thanks. -- Denise B. |
Thread Tools | |
Display Modes | |
|
|