G
Guest
I have reports I need generated from an MS Access 200 database every night. I
created a macro to spit these reports into Excel. I'm on a Windows 2003
Server. I used the 'Scheduled Task' feature to kick off a macro every night
using a batch file that looks like so:
"C:\Program Files\Microsoft Office\Office\msaccess.exe" c:\db\tracklink.mdb
/x excelreport
The last command in the macro is to Quit Acces "saving all".
When I run the macro, it runs fine. When I right click on the scheduled
task, it runs fine. ***BUT*** every morning I log in to see that these
reports haven't been created. I look at the scheduled task and the status
says it's STILL RUNNING. Does anyone know why I'd be able to run the macro
fine, kick off the scheduled task and have it run fine, but when I let the
scheduled task pick up on its own, it just hangs?
I thought MAYBE it was because I had the Quit command "SAVING ALL" instead
of just exiting outright, but I have another access/macro that's scheduled in
a different database that quits the same way that never has a problem.
Needless to say, I either have to keep myself up *EVERY* night of the week
to RDP into the client's machine to make sure this runs properly, or I'll
have one extremely irritated client. I'm losing my faith in MS Access.
Has anyone ever run into anything like this?
Brian Lorraine
(e-mail address removed)
created a macro to spit these reports into Excel. I'm on a Windows 2003
Server. I used the 'Scheduled Task' feature to kick off a macro every night
using a batch file that looks like so:
"C:\Program Files\Microsoft Office\Office\msaccess.exe" c:\db\tracklink.mdb
/x excelreport
The last command in the macro is to Quit Acces "saving all".
When I run the macro, it runs fine. When I right click on the scheduled
task, it runs fine. ***BUT*** every morning I log in to see that these
reports haven't been created. I look at the scheduled task and the status
says it's STILL RUNNING. Does anyone know why I'd be able to run the macro
fine, kick off the scheduled task and have it run fine, but when I let the
scheduled task pick up on its own, it just hangs?
I thought MAYBE it was because I had the Quit command "SAVING ALL" instead
of just exiting outright, but I have another access/macro that's scheduled in
a different database that quits the same way that never has a problem.
Needless to say, I either have to keep myself up *EVERY* night of the week
to RDP into the client's machine to make sure this runs properly, or I'll
have one extremely irritated client. I'm losing my faith in MS Access.
Has anyone ever run into anything like this?
Brian Lorraine
(e-mail address removed)