By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,466 Members | 1,172 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,466 IT Pros & Developers. It's quick & easy.

subquery acting up

P: n/a
JT
I'm using access 2000 and with assistance thought I had this problem
licked.

This query works:
SELECT Q3.id, Q3.date, Max(Q3.Rank) AS Ninetieth
FROM query3 AS Q3
WHERE (((Q3.Rank)<=(0.9*(SELECT COUNT([*]) FROM query3 as Q3A WHERE
(Q3A.ID = Q3.ID) AND (Q3A.[date] = Q3.[date])))))
GROUP BY Q3.id, Q3.date;

This query locks up Access, "action will reset current code in break
mode".
SELECT Q3.id, Q3.medate, Max(Q3.meRank) AS Ninetieth
FROM qry90th1 AS Q3
WHERE (((Q3.meRank)<=(0.9*(SELECT COUNT(*) FROM qry90th1 as Q3A WHERE
(q3.ID = Q3A.ID) AND (q3.[medate] = Q3A.[medate])))))
GROUP BY Q3.id, Q3.medate;

They're both based on the same query, one is query3 and the other is
just a renamed copy of query3. The query3 returns a [rank] for
individual [results] grouped by [id] and [date]. Query3 returns only
31 records, so this should be a quick query.

Any suggestions to why the subquery would cause Access to lockup? I
thought it was just my computer, because I got the first query to work
on another computer, after having the same problem.

Thanks,
JT

Nov 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.