Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Which workbook is stuck in memory
I have several workbooks that are updated overnight, using
vbscript to open the workbook and run its code, then close the workbook. The workbooks are updating just fine, but there is always a copy of Excel left open in memory. I have to go into Task Manager each day and kill it from there. I've used error handing and log files and such to try to get these workbooks to tell me what they don't like, but no errors are occuring. I've also made sure that my vbscripts all contain code to quit the Excel application. Is there a way I can find out which workbook caused the Excel App to be left open in memory? tod |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
XL 2007 - Out of Memory - memory leak/bug? | Excel Discussion (Misc queries) | |||
Users stuck, not logging out of shared workbook | Excel Discussion (Misc queries) | |||
Moving workbook to memory stick - hyperlinks fail | Excel Discussion (Misc queries) | |||
Closed workbook remains in memory. | Excel Programming | |||
The instruction at "0x65255ac9" referenced memory at "0x00000008". The memory could not be read. Clikc OK to terminate etc | Excel Programming |