Report Showing Primary Keys instead of Names!

[kellem80]

I have a report based on a Query. The Query, when run, displays the Project Names and Task Names. When creating the report (report wizard), Access reverts all the Project and Task Names back to thier primary keys. The report is broken down as such:
Project
Task
Activity
Sum Amount

Project is diplaying primary key # in Project Header instead of the name displayed in the query
Task is displaying primary key # in the Task Header instead of the name displayed in the query
Activity in the Activity Header is the Activity Name (which is what is desired), however in the footer, this also ends up reverting to the primary key!!!
The footers contains subtotal and total information (each level has a footer total and all are displaying primary key instead of name associated).

I could not find any help in properties for these fields in the design side, the properties look properly linked.

thanks in advance!
k

 

[HiTechCoach]

Sounds like the evils of Look up field properties in your tables are getting you. See:The Evils of Lookup Fields in Tables

You will need to add the lookup tables to your query. Then add the description fields to your query that you want o use on your report.

 

[kellem80]

Thanks, this helped and worked just fine.
I read the "evils" but what would be an alternative to using the lookup fields that would provide the users the same effect? (Pull-down menus, inability to enter typed characters, etc.) The option would also need to be easy enough to be maintained by Access novices.
Figured I'd ask

 

[HiTechCoach]

The "evil" look up fields only work in tables and queries. Data entry should never be done directly into tables and queries. You should always use a form fopr dat aentry.

Foirms are very powerful. YIu can use a combo box to look up the value from a look up table just like the look up field in a table. Before the feature was added to Access we only way to handle it was on a form. Every Access Guru/Expert/MVP I know all agree that users should never see tables. That means they will never do data entry directly into a table or query. With a well design relational database it is very difficult to do. That may be why Microsoft thought adding the look up to the tables was a good idea. I see it as only encouraging poor Access application development.