<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650285420-29052003>Barb,</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650285420-29052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=650285420-29052003>
That's a pretty heavy duty report. Without seeing it directly, it's
difficult to say if it could be optimized or not. So a couple of general
suggestions:</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650285420-29052003></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=650285420-29052003>1.
Optimize current report - i.e. are fields that need to be indexed indexed, move
calculations up to the highest query level, etc.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=650285420-29052003>2.
Prebuild some of the data in temp tables.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650285420-29052003>3. Break up into separate reports - I
do understand that they need to submit all this info, but does it really need to
be on "one" report. Is the end customer going to know that it was 5
reports that printed a page apiece or 1 report that printed 5
pages?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=650285420-29052003></SPAN></FONT><FONT face=Arial color=#0000ff
size=2><SPAN class=650285420-29052003></SPAN></FONT><FONT face=Arial
color=#0000ff size=2><SPAN class=650285420-29052003></SPAN></FONT> </DIV>
<P><FONT size=2>Jim Dettman<BR>President,<BR>Online Computer Services of WNY,
Inc.<BR>(315) 699-3443<BR>jimdettman@earthlink.net </FONT></P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
accessd-bounces@databaseadvisors.com
[mailto:accessd-bounces@databaseadvisors.com]<B>On Behalf Of </B>Barbara
Ryan<BR><B>Sent:</B> Thursday, May 29, 2003 3:17 PM<BR><B>To:</B> Access
List<BR><B>Subject:</B> [AccessD] VERY SLOW report <BR><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>I have an Access 97 report that runs VERY slowly
(I mean, like an hour or more at times!). Any suggestions you can offer
would be greatly appreciated.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The report header contains 5 subreports.
The detail section contains 7 subreports. Each subreport contains,on
average, appr. 3 detail lines and 1 total line. There are appr. 36
calculated fields per subreport. There are 54 calculated fields in
the detail section of the main report --- SO, 36 x 7 subreports + 54 = 306
calculated fields in each detail section of the report. Each detail
section is printed on a new page.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The report is often more than 100 pages.
There are appr. 20 tables used in the various queries of the main report and
subreports.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The client needs all of this info in one
report. It is their Proposal that they submit when bidding on a
contract, containing all of the labor rates, fringe benefits, overhead,
profit, etc. for each union trade and level (i.e., carpenter foreman,
carpenter journeyman, etc.) for straight time/overtime/double time for first
shift, second shift, third shift.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Help! </FONT></DIV>
<DIV><FONT face=Arial size=2>Barb Ryan</FONT></DIV></BLOCKQUOTE></BODY></HTML>