Form doesn't sort records per the underlying query

[Dirk Goldgar]

When I click "About Microsoft Access" I get: Microsoft Access 2000
(9.0.3821 SR-1)

I don't think you have applied all service packs, so you may want to visit
Office Update and do that. However, you have appplied the most important
one (SR1), and I don't have any reason to believe any later service packs
would affect the issue you're experiencing.

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?

I don't believe so. I would be very surprised if the complexity of the
where-condition had any effect on the form's sort sequence. On the other
hand, I don't yet understand what accounts for the behavior you report, so I
won't make an absolute statement.

 

[Dirk Goldgar]

I did BOTH of those things (actually the property sheet shows my OrderBy
property is blank). I did put the line of code in my OnOpen event but
that didn't fix the problem.

That perplexes me, and I'll have to do some experimenting to see if I can
reproduce your problem. There's always the possibility that yuor form is
corrupted in some way, but I think that is much less llikely than that just
haven't yet hit on the cause of the behavior.

 

[Fred]

I'm not in the same expertise league as these other guys but here's something
to try that that only takes 30 seconds and is a good thing to do anyway.
Open the query in design view and in it's properties (not the SQL or grid)
make sure the "order by" property is empty.

 

[Marshall Barton]

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.

 

[Dirk Goldgar]

I'm not in the same expertise league as these other guys but here's
something
to try that that only takes 30 seconds and is a good thing to do anyway.
Open the query in design view and in it's properties (not the SQL or grid)
make sure the "order by" property is empty.

I would certainly recommend doing this, even though I can't (so far)
reproduce any effect on the form of the query's Order By property. Still,
I'm using Access 2003, not 2000, so there could be a difference between my
system and Dr. Ford's.

 

[Dirk Goldgar]

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 assumed he meant *domain* aggregate functions, such as DLookup -- although
I could conceive of having an aggregate subquery.

 

[John S. Ford, MD]

Dear Fred,

I tried that. Both the filter and order by properties are blank.

John