Report shows record number instead of data
Table#1 = list of companies
Table#2 = associated information
Table#2 uses table#1 as a data source (drop down / combo box...)
Query using table#2 list the company names assocatie with the data
When I build a report using the query above, I only get the record number assocaited with that company name (auto numbering ID).
My question is how do I get the company name instead of the record number of the company?
tnx's b2
Table#2 = associated information
Table#2 uses table#1 as a data source (drop down / combo box...)
Query using table#2 list the company names assocatie with the data
When I build a report using the query above, I only get the record number assocaited with that company name (auto numbering ID).
My question is how do I get the company name instead of the record number of the company?
tnx's b2
ASKER
Ok... so I have this list of companies that I don't want to have to type in very time
So I build a form and add the combo box there ?
Is there a wizard available for me to use while buiding the form for this lookup.
I usually use the form wizard to build the form from the table and then move the fiields around and it already has the correct code to find the lookup table and correct column.
b2
So I build a form and add the combo box there ?
Is there a wizard available for me to use while buiding the form for this lookup.
I usually use the form wizard to build the form from the table and then move the fiields around and it already has the correct code to find the lookup table and correct column.
b2
"So I build a form and add the combo box there ?"
Yes, exactly. Forms are for this purpose - the create a user friendly user interface. Tables are for storing raw data and not really meant to be used by end users. Therefore, it's prudent to avoid using that combo box feature of tables. I have seen it lead to LOADS of confusion ... and it's very difficult to trouble shoot.
mx
Yes, exactly. Forms are for this purpose - the create a user friendly user interface. Tables are for storing raw data and not really meant to be used by end users. Therefore, it's prudent to avoid using that combo box feature of tables. I have seen it lead to LOADS of confusion ... and it's very difficult to trouble shoot.
mx
ASKER
Ok
I like your thought process..
I built a form with the look up table / combo box but still have the same problem...
Now I have a query and report that both show the index number. There must be some relationship that I am missing ?
b2
I like your thought process..
I built a form with the look up table / combo box but still have the same problem...
Now I have a query and report that both show the index number. There must be some relationship that I am missing ?
b2
Can you:
1) Compact & Repair (to shrink the size),
2) Zip up the MDB (to further shrink the size)
3) Attach the file for upload here (using the 'Attach File function below) ... removing any sensitive data of course?
4** And please give a clear explanation of exactly how to reproduce the problem.
mx
1) Compact & Repair (to shrink the size),
2) Zip up the MDB (to further shrink the size)
3) Attach the file for upload here (using the 'Attach File function below) ... removing any sensitive data of course?
4** And please give a clear explanation of exactly how to reproduce the problem.
mx
ASKER
I removed lookup / combo feature on table structure.
I added combo / lookup feature on form.
Form adds index reference to table
Both Query and Report only show index number . I need it to show company name.
b2i
b2.zip
I added combo / lookup feature on form.
Form adds index reference to table
Both Query and Report only show index number . I need it to show company name.
b2i
b2.zip
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Job well done...
no problem and thanks for the kudos ...
mx
mx
This is the problem when you use combo boxes directly in tables, which is really not a good idea. You should remove all combos from that table itself, such that 'what you see is what you get' in any field. As you can see (no pun) ... this is VERY confusing when it comes to queries built on tables with combos for some fields.
mx