With the overnight test, it failed.
We couldn't get any help from our remote network professionals as they knew less that I or my local network guy learned. I finally came to the conclusion, I was beating my head against the wall. Windows scheduled tasks just is not reliable (on our Terminal Server, Windows Server 2003) and the Domain policy or assignment of my user name to the scheduled task security, with full control, wasn't reliable either.
I wasted enough time on this, and decided one morning to write my own Scheduler. I did so, using MS Access 2007. It's been running beautifully since last week, hasn't missed a beat. I also have coded a Timer event in one of my regular databases which monitors the status of my scheduled events, and if they lapse for over 6 hours, I send a popup alert to a key User. This was done in case of a power outage or server outage and my own Scheduler gets disrupted.
I'm off to other work now after solving the problem myself.
Kathy
Access I.T. Consultant