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

Wayne Morgan wrote:

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?