G
Guest
In Access 2003 I have a report that is fed by a "master" query that has 8
layers of queries
below it many of which have one or more of the following features:
1) multiple joins of different types
2) many calculated fields
3) filter criteria
4) grouping and sorting
This master query itself runs with no problem. And up to this point, the
report also runs.
But if I try to add one more set of calculations anywhere in the chain of
queries, when I try to run the report I get the "Query Too Complex" error.
The master query itself still runs but the report will not.
My question is this - are there any general guidelines or specific design
methods, techniques, tips, features, etc. that can be identified that will
help in preventing this "too complex" error.
For example, in one instance I was able to eliminate the error by removing
filtering logic from the Properties screen of the report and inserting an
additional layer of query that performed the filtering. This seemed to imply
that filtering is done more efficiently at the query level than at the report
level.
Are there any other rules I should know? Any help would be great as I seemed
to have maxed-out the computing capabilities of Access but I still have more
features I need to add.
layers of queries
below it many of which have one or more of the following features:
1) multiple joins of different types
2) many calculated fields
3) filter criteria
4) grouping and sorting
This master query itself runs with no problem. And up to this point, the
report also runs.
But if I try to add one more set of calculations anywhere in the chain of
queries, when I try to run the report I get the "Query Too Complex" error.
The master query itself still runs but the report will not.
My question is this - are there any general guidelines or specific design
methods, techniques, tips, features, etc. that can be identified that will
help in preventing this "too complex" error.
For example, in one instance I was able to eliminate the error by removing
filtering logic from the Properties screen of the report and inserting an
additional layer of query that performed the filtering. This seemed to imply
that filtering is done more efficiently at the query level than at the report
level.
Are there any other rules I should know? Any help would be great as I seemed
to have maxed-out the computing capabilities of Access but I still have more
features I need to add.