I’m not sure if nested queries is the correct term for a query that gets it
data from another query. If it is, I am using a heap of queries nested to get
the resultant data for my report but it seems to run very slow.
Is there a way of improving the performance to achieve the same result? The
reason I used this method is that I am not very literate with code.
I appreciate any assistance.
Regards
Nick
Jeff Boyce - 11 Jul 2006 00:53 GMT
Nick
Queries (nested or "chained" - my name for them) can be slow because the
underlying tables are not well-indexed. Is every field you use to join,
select by (criterion), or sort by indexed?
Is there some point in the chain/nest after which the queries slow down (but
they're fast before that point)? Can you post the SQL statement of THAT
(slowed-down) query?
Regards
Jeff Boyce
Microsoft Office/Access MVP
> I'm not sure if nested queries is the correct term for a query that gets
> it
[quoted text clipped - 9 lines]
> Regards
> Nick