We have an Access 2000 app which is supposed to run every morning via the
Windows scheduler using the following command:
"c:\Program Files\Microsoft Office\Office\msaccess.exe"
"d:\FolderName\TheApplication.mdb" /x StartLoad
Where Start Load is a macro which simply calls a procedure, which in turn
call several other procedures, then finishes with the "Quit" command.
The problem is that it appears that Access is either not starting at all, or
it is starting and immediately *** up - it's first task is to write a
text file saying that it has started, and this text file is not showing up.
These are the specifics:
The app is running on NT 2000 running Citrix.
When the system administrator is logged onto the server, the scheduler
opens Access, it runs, and everything is fine, so we think the above command
When he runs the above command from the Run window, everything works fine.
When he is not logged on, we have the problem described above and hours
later the scheduler thinks Access is still running.
He is at a loss and so am I. Does anyone have any idea why Access is either
not opening, or is opening and immediately stopping when the system
administrator is not logged in.