Iordani,

I suppose one way around it would be to use a global variable to store your
parameter value, and set the criterion in the query to read that value from
the global variable through a function instead, so even if Access needs to
rerun the query to sort, it will find the parameter value stored in the
variable again, rather than ask the user for input.
Alternatively, you could use a custom button for sorting, so everything is
handled through code (pass the parameter value and sort the recordset on
opening it), but that is propably more complicated.

HTH,
Nikos

"Savvoulidis Iordanis" wrote in message
...
Access 2000, multiuser MDE app
I use a parameterized query to fill a form or subform with records from a
back end DB in datasheet mode.
The form/subfrm initially does not have any recordsource set.
I manually set the form's recordset in form's open after I fill the parms
of
the query and run it.

qdf.parameters(0).value= xxx
set rst=qdf.openquery...
set me.recordset = rst

I set the recordset this way, so that I don't get the ugly Access
parameter
window when the form opens
and is based on a parameterized query.

All fine up to now.
Now, when I use the sort toolbar button, I get that ugly Access parameter
window. Why?
Doesn't the sort occur on the local recordset in the form? Is access
trying
to requery again?

How can I overcome this?