Description displaying on Report

I have a field that is a listbox on the form.  It stores the CODE but displays the DESCRIPTION.  

I'm making a report, for this field, I want to display the DESCRIPTION but the report field is showing the CODE (because that's what's stored in the field).  

On the report, I turned the field to a list control on the subform (which sits on the report), linking to that list and it's displaying the DESCRIPTION but it's also showing the dropdown arrow from the list... how do I make the data display in a textbox or get rid of the arrow on the list since this is a report.
gcgcitAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dale FyeOwner, Developing Solutions LLCCommented:
Another reason to convert the form to a report (see my original response to your previous post).

I don't know of anyway you can programmatically change the control type of a control on the subform that is embedded in your report.

If you create a report, I would join that field "Code" to the table that is now the rowsource of your listbox, then I would add the [Description] field to the query that is the recordsource for the report.
Nick67Commented:
Agreed with @fyed.
I saw your first question a little earlier.
Create a subreport object!

It's not hard.  Add a new report in design view, open your subform in design view
Copy all the objects from the subform, paste them on the the report.
Open the recordsource of the form, Save as a new query.
Tweak it.  Every combobox on the form can be a join in the report query and then just a textbox.

Although some Experts have disagreed with my adamance, reports are for printing, forms are NOT
Dale FyeOwner, Developing Solutions LLCCommented:
Nick,

Don't remember how easy it was in 2003, but in 2007, you can open the form in design mode and then do a Save As.  When you do this, you can select whether you want to save it as a report or as a form.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Nick67Commented:
That works in A2003, but I've never tried it until just now.
It keeps the exact look of the form, and usually you're trying to match the main report's look.
But it is doable too.
Depending on the source form it may be less work than a copy-paste

But from the earlier question, I agree with @fyed that there is little point in putting code into a form to make it behave like a report.
Just create the report!
gcgcitAuthor Commented:
I just started using 2007 - that was pretty easy to convert to a report so I did.  Looks great. Thanks guys!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.