Report and .ADP file size

[Kyle Jedrusiak]

My app programmatically executes a long query, then it programmatically runs
any one or more of 4 reports.

Reports 1, 2 and 3 seem to run fine (leading me to believe that the query
has finiahed.)...Report 4 never generates and just puts the program in what
LOOKS like and infinite loop.

If I break the program and manually run the report it opens in second and
cursory inspection shows the data to be good.

The thing that I did notice is that the size of the .ADP file grows from
it's initial size while things are running.

Don't know that this is related directly...but would like to know what I'm
doing to cause the .ADP file to expand in size. (Wondering if that's
related to the issue.)

Kyle Jedrusiak

 

[Tom van Stiphout]

On Tue, 20 Jan 2009 16:42:02 -0500, "Kyle Jedrusiak"

I would first run the 4th query in SQL Server Management Studio and
see if it ran slowly there as well. If yes, you know what you need to
optimize. If no, something about the design of the 4th report is not
in order. Create a new junk report with the same query as the
RecordSource and see how you fare.

-Tom.
Microsoft Access MVP

 

[Sylvain Lafontaine]

Maybe you have some locking problem on the server because your code is not
closing one or more recordset or something like that. You should take a
look with the Profiler and also verify with the stored procedure sp_lock
that there is no lock left when you try to open the fourth report.

Another possibility would be that you have some of corruption. You could
create a blank ADP project and import all the items or import the fourth
report and see what does this give.

The growing size of the ADP project is a normal process (of course, if this
is not growing up exponentially) and like MDB files, you should compact it
from time to time. This will particularly happen if your code is making
modifications to the reports in design mode.