John S. Ford, MD wrote:
When I click "About Microsoft Access" I get: Microsoft Access 2000
(9.0.3821 SR-1)
It seems like the WHERE argument disables the query's inherent sort routine.
I'm surprised that the WHERE argument can do this but let me ask you one
question.

the WHERE statement is quite complex and uses aggregate functions. Could
the use of aggregate functions in a WHERE statement do "more" than just
filter the query its acting on?


PMFJI, but I am concerned that you do not have a clear
picture of the query. You said,:
"the WHERE statement is quite complex
and uses aggregate functions",
BUT, AFAIK, a WHERE clause can not contain aggregate
functions. That is the province of the HAVING clause.
Getting mixed up on which is which can cause the query to
produce an unexpected result.

I don't see how any of this can affect the sorting though.

--
Marsh
MVP [MS Access]