planetthoughtful wrote in message
<1143683644.917026.67890@t31g2000cwb.googlegroups.com> :
> Probably because without any SORT BY clause in the query, Access will
> natively sort by the table's primary key, which in the OP's post I'd
> guess is an autonumber field.
As I've understood, an ORDER BY clause, is not necessary for an
ordinary
ranking query to work, I like to add it though, to present the result
in
the same order as the ranking, but again, I don't think it is entirely
necessary. If you look again, you should be able to find an ORDER BY
clause as the last clause of my suggested SQL statement.
Using Count(*), will usually also do, in stead of Count(FieldName), I
don't know why I keep using the latter version.
But I do think you need a sortable and unique *field*, on which to set
the criterion in the subquery. If the field isn't unique, equal
values/duplicates will get equal rank.
For more samples/explanations, check out for instance
http://support.microsoft.com/kb/q182568/
http://www.fabalou.com/Access/Queries/RunningTotalQuery.asp
http://ourworld.compuserve.com/homepages/attac-cg/AqryTip.htm#AUTONUM
If I've competely misunderstood the concept of "Ranking queries" or
"Running totals", I'm happy to learn new ways (except usage of Domain
Aggregates, that is).

Signature
Roy-Vidar