Starnge Issue

[GeoNelix]

Hello,
I have a scheduled task that opens a version of Access 2000 and runs a process. This process includes sending reports to clients via outlook and redemption. When I log into the server to take a look at the process I see literally 100's of the same report trying to open and the process is stalled. The Microsoft Access for Windows bar that is displayed on the desktop taskbar shows something like this > 452 Microsoft Access for Windows and when you click on it the same report is listed hundreds of times. Has anyone seen this before? Thanks in advance!

 

[KenHigg]

Sounds like you're not closing Access after each report opens and runs (?)

 

[GeoNelix]

The process loops through a recordset and sends reports out that are in that recordset. So no, Access closes only after all reports are sent out - after the loop runs. Do I need to open a version of access for EACH report that needs to be sent out?

 

[KenHigg]

It appeared as though an instance of Access was opening, or maybe calling a windows API each time the thing looped and windows was getting ahead of Access. Maybe a strategically placed 'DoEvents' command?

 

[GeoNelix]

hmmm - never thought of that - I'll look into it - thanks for your quick response!

 

[The_Doc_Man]

Concur with Ken regarding DoEvents, it never hurts. But ...

It sounds to me like you are violating one of the fundamental rules of programming (not limited to Access or even to Windows). You must always close what you open.

However, it becomes important to know HOW you are sending the report. For that many instances of Access to be open, I wonder if you are sending something via embedded OLE and you are getting hammered with remote OLE requests.

If that is the case, the REAL problem is that you CAN'T close what you opened because this time you didn't open them. Outlook did.

If this fits your situation, you need to look into changing your method of sending reports.