My report does not seem to see columns created in the underlying query

[John_sc]

I created a query ReportQuery. I am trying to display a calculated field in my report. It shows up in the query - I can see it. But the report is giving me the error that it does not find this field. The filed gives me any text beyond 255 characters in a memo field.

ExtendedText: IIf(Len([CleanText])>255,Mid([CleanText],256),"")

In the report I reference ReportQuery.ExtendedText as the control source.

[ranman256]

That is hard to believe. All fields in the query should be visible to the report.

[JamesDeckert]

So running the query by itself works? (shows field info longer than 255)
And the report has the query as it's record source?
Then the control source for the field should work with ExtendedText as the control source as long as this is the same spelling in the query.
Is ExtendedText available when you click the dropdown of fields to choose from on the control source?

[John_sc]

This is why I posted the question. My experience indicated I should have been able to see calculated field. In fact, I have other calculated fields in the query, and I can see those.

One out of the ordinary thing I am doing is that I placed a parameter in the query. (not sure if this is the proper term) As one of my criteria, I entered the condition [Enter Target Date], which is not a field. When the query runs, it asks the user to [Enter Target Date], which is then used to constrain the query. This works fine. but I don't get the calculated fields.

To try to debug things, I removed this parameter, and modified the report, but it still seems to be using the old query. The query does not ask for the date, but the report does. The calculated fields I can not see were added later than the ones I can see. So it seems that I need to somehow refresh the query request from the report. Any ideas?

[John_sc]

Found the problem. The record source was a query itself - it did not just reference the other query. The query in the report explicitly listed the fields, which did not include my new calculated fields. I think once I update this, it should work.