J
jmarkron
I have successfully deployed an MSAccess2007.accdb on a server that logs-in
(SHORTCUT: /User & /Pwd), runs through an AUTOEXEC logic, runs a MACRO of
logic and then automatically ends/exits. It works fine when I'm logged onto
the server and there is an active screen/monitor for the forms and messages
(mostly saying that things are getting done). However, it dies as soon as
the WindowsTaskScheduler starts it and I'm logged-off or it runs with the
screen-saver locked (no screen/monitor). How can I have the freedom of it
AUTORunning without my attention?
My past solution was to create a VMmachine that boots with an auto-log-in
(WindowsTaskScheduler launches the app) and never sleeps. It works fine and
no one else is allowed to log-in. It is an expensive solution for a problem
within MSAccess.
Any ideas? ........Ron
(SHORTCUT: /User & /Pwd), runs through an AUTOEXEC logic, runs a MACRO of
logic and then automatically ends/exits. It works fine when I'm logged onto
the server and there is an active screen/monitor for the forms and messages
(mostly saying that things are getting done). However, it dies as soon as
the WindowsTaskScheduler starts it and I'm logged-off or it runs with the
screen-saver locked (no screen/monitor). How can I have the freedom of it
AUTORunning without my attention?
My past solution was to create a VMmachine that boots with an auto-log-in
(WindowsTaskScheduler launches the app) and never sleeps. It works fine and
no one else is allowed to log-in. It is an expensive solution for a problem
within MSAccess.
Any ideas? ........Ron