M
Mike
I have automated my database to run during non peak times when no one is
around and so that the Current data will be available when they come in the
next morning.
The problem I'm having is that when the database opens at the scheduled time
(Windows scheduler) it launches creates the links and then hangs there until
I come in in the morning and log on to my computer.
Windows Scheduler allows me to store my user ID and password, so this should
not be an issue.
Once I log in the database continues without any input on my behalf.
This whole delay is causing problem as the data is not available to the end
users at the needed times.
Does anyone have a thought on this or run into a similar experience?
around and so that the Current data will be available when they come in the
next morning.
The problem I'm having is that when the database opens at the scheduled time
(Windows scheduler) it launches creates the links and then hangs there until
I come in in the morning and log on to my computer.
Windows Scheduler allows me to store my user ID and password, so this should
not be an issue.
Once I log in the database continues without any input on my behalf.
This whole delay is causing problem as the data is not available to the end
users at the needed times.
Does anyone have a thought on this or run into a similar experience?