Out of memory generating reports in batch

[vbaInet]

You should go right back to the basics. Use two separate reports for those queries and don't set the record source in design manually.

Can you see the effects on the Task Manager?

Yep, I meant an attachment.

 

[Cris]

I am a little confused. If I don't set the record query in desing manually and I don't set it in the Report_Open Event, when it should be setted?

I am not sure I am understanding.

 

[vbaInet]

That was supposed to read:

"Use two separate reports for those queries and don't set the record source in code. Set it in design view manually."

 

[Cris]

Ok, now i understand. Thanks.

And for the DB, unfortunately i am not sure I can send it you because of confidentially politics with my client i am going to see if i can do something.

When i make the test i always check on the Task Manager. It is there when i am monitoring the increasing in memory usage. When i open the report it increase, when it is close it decrease but not to the point where it started, so it always accumulating.

I have already test putting the query in desing mode but without openning the report, just sending it to pdf with the outputTo and changing the querydefs. This is still consumming memory, but i get to generate more reports since i don't open the report. However, the outputTo doesn't catch the out of memory error so if computer runs out of memory Access just freeze.

I am going to try the query in design mode with the open report.

 

[vbaInet]

I have already test putting the query in desing mode but without openning the report, just sending it to pdf with the outputTo and changing the querydefs. This is still consumming memory, but i get to generate more reports since i don't open the report. However, the outputTo doesn't catch the out of memory error so if computer runs out of memory Access just freeze.

So I think we've established that the problem is coming from OutputTo. You could try to re-install the Add-In:
http://www.microsoft.com/downloads/...3c-6d89-4f15-991b-63b07ba5f2e5&displaylang=en

Also try it on a different printer too.

 

[Cris]

I am not sure the problem is the outputTo statement because i had already tested just oppening the report and closing it after that and the problem is the same.


I am goint to try to re-install the Add-in anyway.

 

[vbaInet]

I think at this stage it would be impossible to detect the problem without seeing the db.