Running Access as a Windows Scheduled Task

  • Thread starter Thread starter Jean
  • Start date Start date
J

Jean

I'm not sure which newsgroup this problem fits best so
please let me know if it would be better posted in another
newsgroup.

I have an Access 2000 program that I am executing from a
batch file as a Windows Scheduled Task with the following
command line:
"C:\Program Files\Microsoft
Office\Office\MSAccess.exe" "C:\Program
Files\TK_FrontEnd\Data\DTStats.mdb" /nostartup /runtime /cm
d "Import"

I then have an Autoexec macro within Access to read the
cmd argument and do some processing.

The scheduled task works fine if the Windows account
logged on is the one running the task. However, if the
task is run under a different account, Access either opens
(I see the .ldb file appear) and does nothing or Access
never opens at all. Setting Administrator permissions for
the account running the task doesn't seem to make any
difference in the outcome.

Any help is greatly appreciated.

Thanks,
Jean
 
This is out of my own area of expertise, but maybe this will help: If the db
performs a series of actions, put a msgbox (or whatever) after each few
steps. Perhaps it is stopping on some specific step, when it is run from a
different account. If you knew what step that was, the cause might become
obvious.

If you can't display a msgbox in your particular situation, write the
messages to a file. Remember to close & reopen the file (four poutput
append) after writing each message,m to ensure that the message is actually
flushed to disk, not just left in a buffer somewhere.

HTH,
TC
 
Back
Top