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?

--
Wayne Morgan
Microsoft Access MVP


"Mark Hubbard" wrote in message
...
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.