Stray Field

  • Thread starter Thread starter Mark Hubbard
  • Start date Start date
M

Mark Hubbard

I am using Access 2000 wizards to make a straightforward report from an
existing query. All the query fields will be present in the report and
teh query itself works fine. The report, however, even after three
attempts at starting over, keeps asking for a 'rogue' field from a table
elsewhere in the db when I try to run the report. I can easily hit
'enter' and get past this pop-up box asking for this and the ensuing
report is then ok, but I am confounded as to why this keeps happening.
Thanks in advance.
 
When "hidden" parameters such as this pop-up, I frequently find them in the
Sorting and Grouping dialog. Also, check your spelling on the field names in
the control sources of the controls on the report and look for any hidden
controls. Open the report, go to the immediate window, and type

?Reports!ReportName.Controls.Count

Press Enter, what is the number that is returned? Count the controls in the
report, can you account for all of them? Lines, shapes, labels, everything
should be included in the count.
 
Everything you mentioned is in good shape. Thanks for your reply. Any
ideas on renaming the rogue field or other method of tearing stuff down
and rebuilding it would be greatly appreciated.
Mark
 
If the query isn't prompting for the parameter, then it doesn't appear to be
in the query. So it has to be in the report. The only way to get the report
to prompt for the value is to have it listed as a field that isn't available
in the query feeding the report. I don't know if the wizard is doing
something strange, have you tried creating the report manually? Perhaps just
a quick report, dragging and dropping all of the available fields into the
report and open it just to see what happens.

Do you have any comboboxes on the report? This may have happened if you
defined a lookup field in the table or query and it propagated to the
report. If so, is this rogue field in the Row Source of the combobox?
 
Ah, in creating the test report manually when I went to bind it to the
query I noticed it had dragged the rogue field into the 'order by'
parameter. I still do not know why It did this but at least the real
report I am using is fixed now. Thanks again.
Mark
 
Back
Top