Report Opening Speed

[FBxiii]

Hi.

I have 3 reports based on the same query which is used to calculate charges.
Each report has its own query to display the charges grouped in different
ways - By Customer, by Customer "Owner" and the 3rd by Customer "Owner" and
Customer.

2 of the reports process within a couple of minutes but another takes about
30! The problem report is the one by Customer only.

I know this is a bit of an open question, but can anyone give me any advice
to why this may be?

Thanx,
Steve.

 

[Allen Browne]

If they are based on the same query, the problem won't be with indexing of
the fields. It is most likely within the report itself.

Take a look at the properties you have set for the sections of the report:
in the Properties box, or in the lower pane of the Sorting And Grouping box
(View menu.) What settings could be causing Access to do lots of layout and
retreating?

For example, if you set the Keep Together property in the lower pane of the
Sorting and Grouping box to Whole Group, this is very likely to cause Access
to calculate a layout, discover it doesn't fit, and have to retreat back
through all the detail records it was trying to fit on the page under this
header. Especially where sections can grow or can shrink, this kind of thing
can really slow down the calculation of the layout of the pages.

Obviously, any code you have in the report's module is a factor as well. For
example, if you use code in the Format event of the Detail section to
highlight a field when a condition is met, you can speed the report up by
dumping the code and using Conditional Formatting instead (Format menu, in
report design.)

If you can't find the cause, you might try adding some code to the Format
event of the Detail section, logging the primary key values to a table, so
you can examine what sections are being formatted, and what retreating is
taking place.

All this is assuming that you have already taken the basic steps of turning
off Name AutoCorrect, subdatasheets and so on. Tony Toews has this general
list here:
http://www.granite.ab.ca/access/performancefaq.htm

But since the other reports work fine, it would seem to be something this
particular report is doing that the others are not.

 

[FBxiii]

Hi.

Thanks for the reply. I have found the query was calling some code which
was lagging the report up!

The function is not needed in these particular reports so I have removed it
and it now runs in more or less the same time as the others.

Cheers!
Steve.