I have an Access application that sends out email about new hires, terms and other employee information. The code for this process resides on a "startup" form. The form opens, processes the data, sends email and then quits the application. Works beutifully when run manually.
I wanted to automate this application and used Winbatch, a Windows batch processing program, and Windows Task Scheduler to run it at a set time every day. When left unattended the task will start but appears to "freeze". I can go in and see that the database was opened, the "ldb" file apears, but nothing happens. The job never completes. The only way to stop is to kill the task in Task Scheduler. At that time the "ldb" file is left out there and it can not be deleted. The error message is that there is a "sharing violation". I can use Task Manager to stop MS Access and then delete the "ldb" file.
Any ideas why this runs manualy but not with Windows Task Scheduler?
I wanted to automate this application and used Winbatch, a Windows batch processing program, and Windows Task Scheduler to run it at a set time every day. When left unattended the task will start but appears to "freeze". I can go in and see that the database was opened, the "ldb" file apears, but nothing happens. The job never completes. The only way to stop is to kill the task in Task Scheduler. At that time the "ldb" file is left out there and it can not be deleted. The error message is that there is a "sharing violation". I can use Task Manager to stop MS Access and then delete the "ldb" file.
Any ideas why this runs manualy but not with Windows Task Scheduler?