Making it an mde would have almost zero effect on the speed.

Yes, running the query before hand should have NO effect on the speed of the
report. Try it without running the query first and see if you get any change.

As an experiment - make a copy of the report and remove the sub-reports. How
fast is it?

Now make a copy and remove three of the four sub-reports? How fast is it?

Repeat for all the sub-reports and see if any specific sub-report is the
culprit. If so, work on speeding that up.

Sub-reports can slow down a report significantly. Without being able to
actually see the report it is difficult to tell you what the exact problem is
or could be.

John Spencer
Access MVP 2002-2005, 2007-2010
The Hilltop Institute
University of Maryland Baltimore County

mrPela wrote:
Yes' It's a simple select query. The reason I do it is because I want to
limit the results to only a specific group. There are thousands of records,
and I only need records for a specific group of records. So in the query that
I'm running prior, I identify which group I want.

are you telling me that doesn't have an affect?

Also - my db is split (front end/back end). However it's not an .MDE. If I
were to make it one, how would that improve this performance issue I'm having.


mrPela wrote:
John - I am using subReports, I apologize. I wasn't querying the actual query
associated with the sub report. However, there are maybe 2 or 3 queries that
support the query for a sub Report. Therefore the 1 query that supports the
query is the one I'm updating which in theory I would think would make the
main query easier to open, NO???

First of all, there is no good reason to run a query before opening a report.
The report and the sub-reports will call the queries independently. So
[quoted text clipped - 18 lines]
the report. What are some things that I can do to make this report open a lot
quicker?