Report pulling record primary key instead of text

[librarian]

I have a table of journal subscriptions that contains the following fields:

• Subscription title - text
• Subscribers - Lookup & relationship field. This pulls the autonumber primary key, first name and last name from an employee table. It only displays the first & last name of each record when viewing the dropdown box to make a selection (the primary key is just used to distinguish between records) and multiple records can be selected.

From this table, I have two forms that pull queries - one gives the option to select a title and view all of the names of subscribers, and the other gives the option to select an individual subscriber and see all of the titles he/she subscribes to. If the forms point to their queries, all is well. The query by title displays a Subscription column with the title in it and a Subscribers column with the last names seperated by commas of all the individual subscribers. The query by individual subscribers displays a Subscription column with each title in its own row and a column titled tblSubscript that contains the last name of the individual queried (the same name over and over again in each row).



Once I try to create a report based on these two queries, however, the areas where the last names are displayed in the queries are only showing the primary key autonumber for their corresponding records. I would like the report to display the last names as opposed to this number (or, in a really ideal situation, the first and last names), but I'm not sure where to do this. I understand that the autonumber is the defining field used to pull each record, but it doesn't really give the person viewing the report the information they need. I can't change the last name to the primary key since this is a pretty large table of subscribers and their last names won't always be unique. I realize if only the last names are displayed some may be repeated or the report's viewer may not be able to tell two identical names apart, so having first and last name would be the best case scenario, but even just having the last name shown would be good enough.

Thank you in advance for any help!!

PS - sorry for the terrible thread title, I didn't really think about it until I hit post and now I'm stuck with it

[pbaldy]

See this, specifically #5:

http://access.mvps.org/access/lookupfields.htm

[jzwp11]

What you describe is one reason not to use lookups at the table level. See this site for more problems table level lookups can cause.

Do the queries you mention include the employee table? If not, you will want to add it to the queries & then you should be able to pull the names (first & last) into your report.

oops I see Paul beat me to the punch!