phantom field

  • Thread starter Thread starter Erica Burton via AccessMonster.com
  • Start date Start date
E

Erica Burton via AccessMonster.com

I have a report based on a query that I want to use as a template (because
I'm lazy and don't want to lay it all out again). I thought I'd be smart
and just change the query name in the Report's 'record source' for each
successive report. My problem is that when I run the I run the report, it
still asks me for a parameter from the previous query (used for record
source). I hope I've made sense.

Any suggestions?
 
Hi Erica,

- How are you changing the 'recordsource'? Programmatically?
- Is the parameter in the report (part of the report definition)?

Immanuel Sibero
 
I have a report based on a query that I want to use as a template (because
I'm lazy and don't want to lay it all out again). I thought I'd be smart
and just change the query name in the Report's 'record source' for each
successive report. My problem is that when I run the I run the report, it
still asks me for a parameter from the previous query (used for record
source). I hope I've made sense.

Any suggestions?
Click to expand...

In all probability you have a reference remaining to a field in the
previous report that you haven't changed.
The usual culprit is the report's Sorting and Grouping dialog....
View + Sorting and Grouping.
 
Hi Immanuel,

I'm not a very good programmer, I'm afraid it's the brute force method for
me. I've just gone into my 'copied' report and manually changed the name
of the query.

I've changed the names of the fields that appear on the report to
correspond with the fields in the new query, so that the 'old field', as
far as I can tell, does not appear anywhere in the body of the report.

The report runs fine if I ignore (hit return) the dialog box that asks for
the 'old field' to be entered. It's if it's hanging over in a register
somewhere but I don't now how to clear it.
 
Back
Top