Report Textbox prints ID number, not text

Zipdoc

New member
Local time
Today, 03:07
Joined
Dec 18, 2009
Messages
4
Ok, this is probably something really simple, but it's driving me to drink (more). I have a report based on a simple query that lists a lectures based on overall subject topics. I would like to also list the course section within which the lecture is given:

Overall Subject Heading
Section Title
Lecture Title
When I run the query, it's perfect; everything displays the way it should. However, when I run the report, the Section Title displays as a number (I assume the ID). At first I found the field in the main table for Section Title was set to number. Changed it to text, no effect.

What am I overlooking!? Thanks in advance.

Zipdoc
 
Do you have lookup fields defined at the table level? If so, remove them.

See here for more about that. Then you use a query in your report to link to the table with the text and then bind the report control to the query field.
 
At first I found the field in the main table for Section Title was set to number. Changed it to text, no effect.
And NO - it SHOULD be a number.
 
Thank you for the prompt reply. I do have lookup fields for both, and I read your linked site, but I'm not sure I understand the significance. I used the combobox within the table to try and maintain my data integrity, not to make it worse. In other reports, I haven't had a problem and have been able to add the SectionList table to the query and reference that within the report (as I think you are suggesting to do). For this query, however, I continue to get an error: SQL statement can not be executed due to ambiguous outer joins.

Perhaps this is a query problem and not a report issue? Still don't quite understand why the original query behaves and display correctly in datasheet view.

Thanks in advance for any additional insight.

Zipdoc
 
Thank you for the prompt reply. I do have lookup fields for both, and I read your linked site, but I'm not sure I understand the significance. I used the combobox within the table to try and maintain my data integrity, not to make it worse. In other reports, I haven't had a problem and have been able to add the SectionList table to the query and reference that within the report (as I think you are suggesting to do). For this query, however, I continue to get an error: SQL statement can not be executed due to ambiguous outer joins.

Perhaps this is a query problem and not a report issue? Still don't quite understand why the original query behaves and display correctly in datasheet view.

Thanks in advance for any additional insight.

Zipdoc
Lookup fields at table level will cause all sorts of problems in queries, forms and reports. Get rid of them. It is okay to use them TEMPORARILY in order to have the form wizard set up your combo boxes on your forms, but once that is done you should revert the lookup back to TEXT BOX from Combo Box on the lookup tab in the table design view.
 

Users who are viewing this thread

Back
Top Bottom