(Msg. 1) Posted: Wed Oct 07, 2009 10:54 am
Post subject: slow access 2007 report Archived from groups: microsoft>public>access>reports (more info?)
Is there a good way to try to find out why a report is slow to load. I
thought it was the query underneath, but the query fires pretty quickly,
about afew seconds. Whereas the report could take 30-45 seconds. Thanks for
the help.
(Msg. 2) Posted: Wed Oct 07, 2009 8:26 pm
Post subject: RE: slow access 2007 report [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Does the report have a lot of calculations in it (like subtotals, totals,
grouping and sorting and calculated fields)?
It is faster if you do as much calculation in the query as you can. Of
course you can't to the subtotals and totals in the query, but if you have
any controls on the report that contain calculations, you could add the
calculation to the query. Also, if there are any DSum, DCount, or any other
Domain Aggragate functions in the report and there is a way you could include
it in the form's recordset query, that would help performance.
Using the above methods, I once had a report somebody else wrote that took
90 minutes to run. After I modified it, it took about 5 minutes.
--
Dave Hargis, Microsoft Access MVP
"icccapital" wrote:
> Is there a good way to try to find out why a report is slow to load. I
> thought it was the query underneath, but the query fires pretty quickly,
> about afew seconds. Whereas the report could take 30-45 seconds. Thanks for
> the help.
(Msg. 3) Posted: Thu Oct 08, 2009 5:38 am
Post subject: RE: slow access 2007 report [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
That is good advice, thanks. You mentioned grouping. Is there a way to
speed up grouping? The reason I ask is because when I tried to create a new
blank report based on the query it ran quickly. Once I added one group it
started to slow down already.
"Klatuu" wrote:
> Does the report have a lot of calculations in it (like subtotals, totals,
> grouping and sorting and calculated fields)?
>
> It is faster if you do as much calculation in the query as you can. Of
> course you can't to the subtotals and totals in the query, but if you have
> any controls on the report that contain calculations, you could add the
> calculation to the query. Also, if there are any DSum, DCount, or any other
> Domain Aggragate functions in the report and there is a way you could include
> it in the form's recordset query, that would help performance.
>
> Using the above methods, I once had a report somebody else wrote that took
> 90 minutes to run. After I modified it, it took about 5 minutes.
> --
> Dave Hargis, Microsoft Access MVP
>
>
> "icccapital" wrote:
>
> > Is there a good way to try to find out why a report is slow to load. I
> > thought it was the query underneath, but the query fires pretty quickly,
> > about afew seconds. Whereas the report could take 30-45 seconds. Thanks for
> > the help.
(Msg. 4) Posted: Thu Oct 08, 2009 5:46 am
Post subject: RE: slow access 2007 report [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
No, reports ignore any ORDER BY clause in their row source query, so there is
not much you can do if you need the grouping.
--
Dave Hargis, Microsoft Access MVP
"icccapital" wrote:
> That is good advice, thanks. You mentioned grouping. Is there a way to
> speed up grouping? The reason I ask is because when I tried to create a new
> blank report based on the query it ran quickly. Once I added one group it
> started to slow down already.
>
> "Klatuu" wrote:
>
> > Does the report have a lot of calculations in it (like subtotals, totals,
> > grouping and sorting and calculated fields)?
> >
> > It is faster if you do as much calculation in the query as you can. Of
> > course you can't to the subtotals and totals in the query, but if you have
> > any controls on the report that contain calculations, you could add the
> > calculation to the query. Also, if there are any DSum, DCount, or any other
> > Domain Aggragate functions in the report and there is a way you could include
> > it in the form's recordset query, that would help performance.
> >
> > Using the above methods, I once had a report somebody else wrote that took
> > 90 minutes to run. After I modified it, it took about 5 minutes.
> > --
> > Dave Hargis, Microsoft Access MVP
> >
> >
> > "icccapital" wrote:
> >
> > > Is there a good way to try to find out why a report is slow to load. I
> > > thought it was the query underneath, but the query fires pretty quickly,
> > > about afew seconds. Whereas the report could take 30-45 seconds. Thanks for
> > > the help.
(Msg. 5) Posted: Thu Oct 08, 2009 5:49 am
Post subject: RE: slow access 2007 report [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
thanks, i'll give those other thoughts a try
"Klatuu" wrote:
> No, reports ignore any ORDER BY clause in their row source query, so there is
> not much you can do if you need the grouping.
> --
> Dave Hargis, Microsoft Access MVP
>
>
> "icccapital" wrote:
>
> > That is good advice, thanks. You mentioned grouping. Is there a way to
> > speed up grouping? The reason I ask is because when I tried to create a new
> > blank report based on the query it ran quickly. Once I added one group it
> > started to slow down already.
> >
> > "Klatuu" wrote:
> >
> > > Does the report have a lot of calculations in it (like subtotals, totals,
> > > grouping and sorting and calculated fields)?
> > >
> > > It is faster if you do as much calculation in the query as you can. Of
> > > course you can't to the subtotals and totals in the query, but if you have
> > > any controls on the report that contain calculations, you could add the
> > > calculation to the query. Also, if there are any DSum, DCount, or any other
> > > Domain Aggragate functions in the report and there is a way you could include
> > > it in the form's recordset query, that would help performance.
> > >
> > > Using the above methods, I once had a report somebody else wrote that took
> > > 90 minutes to run. After I modified it, it took about 5 minutes.
> > > --
> > > Dave Hargis, Microsoft Access MVP
> > >
> > >
> > > "icccapital" wrote:
> > >
> > > > Is there a good way to try to find out why a report is slow to load. I
> > > > thought it was the query underneath, but the query fires pretty quickly,
> > > > about afew seconds. Whereas the report could take 30-45 seconds. Thanks for
> > > > the help.
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Home
Forums
Home
FAQ
Profile
Private Messages
Log in
Office Other