I am responsible for the batch running of a number of Impromptu reports created by an external company. Following the creation of each report, a Snapshot is taken of the output and a PDF file is also created.
As the size of the database has increased, I am now finding that it is impossible to complete the execution of the job which creates all these reports.
It would appear that a very large file is being created in a Temp folder - the final size does vary (typically it can exceed 700,000 Kbs) but there still appears to be space on that drive.
I have now proved that this occurs when (in isolation)the Snapshot is being taken; I am certainly able to produce the individual PDF file for that report.
The offending statement reads 'ImpReport.SaveAs **************' (where ********* provides the filename, etc.)
Can someone please advise me how I might overcome this problem.
[Another question is "As the macro does handle the generation of several reports in a single run, is it possible to free up this temporary space once the creation of an individual report has been completed ?"]
As the size of the database has increased, I am now finding that it is impossible to complete the execution of the job which creates all these reports.
It would appear that a very large file is being created in a Temp folder - the final size does vary (typically it can exceed 700,000 Kbs) but there still appears to be space on that drive.
I have now proved that this occurs when (in isolation)the Snapshot is being taken; I am certainly able to produce the individual PDF file for that report.
The offending statement reads 'ImpReport.SaveAs **************' (where ********* provides the filename, etc.)
Can someone please advise me how I might overcome this problem.
[Another question is "As the macro does handle the generation of several reports in a single run, is it possible to free up this temporary space once the creation of an individual report has been completed ?"]