T
Tod
I have some scripts that open workbooks on a server,
updates them by running the workbook's code, then closes
them. They run every day and some run more than once per
day. It works fine until the workbook errors for any
reason. When that happens the workbook pretends to still
be open. There is no instance of Excel open in memory
(Checking Task Manager's Processes tab). The temp file is
there but I can't delete it because of sharing violation.
The only solution is to reboot the server. I'd rather not
reboot the server 2-3 times a day, espcially since I'm
sharing it with someone.
The problem is that there is no error handing yet, in any
of the scripts or VBA code. I'm working on that, and it
should solve my problem. But it's going to take time to
get to them all. In the meantime, could someone offer a
way I can 'unhang' the workbook without rebooting the
server?
tod
updates them by running the workbook's code, then closes
them. They run every day and some run more than once per
day. It works fine until the workbook errors for any
reason. When that happens the workbook pretends to still
be open. There is no instance of Excel open in memory
(Checking Task Manager's Processes tab). The temp file is
there but I can't delete it because of sharing violation.
The only solution is to reboot the server. I'd rather not
reboot the server 2-3 times a day, espcially since I'm
sharing it with someone.
The problem is that there is no error handing yet, in any
of the scripts or VBA code. I'm working on that, and it
should solve my problem. But it's going to take time to
get to them all. In the meantime, could someone offer a
way I can 'unhang' the workbook without rebooting the
server?
tod