We changed the user/pw to an administrative account that was created for this purpose and it worked for years.
Make sure "wake the computer to run this task" is set. If not, it may not run under the circumstances you cite.
Also, remove all that Access stuff in the "run" command. Just reference the Access file name where your Autoexec is located or the Excel file name where your Autpen is located.
George,
Thanks for the pointers. I am running on XP professional, and just scheduling it a minute from now. Tried Scheduler to open Excel, and even a difft Access dbase. It does that. I did go ahead and select "Wake Computer", and again tried running without the "Run Only if Logged on", but these are not doing the trick.
Question: The stuff on the Run command line in Scheduler allows our secure DB to open (it is passworded so I place the userid and pwd in this line) And, the macro switch that I have on the Run line ( \X mcrOpenForm ) is what tells Access to open the Form in my dbase (I have my code sitting on the OnOpen event of that Form). All runs fine, on schedule, if I do not bring up Windows security.... Very frustrating.
I am curious though about what you say: "Just reference the Access file name where your Autoexec is located ". I guess I do not have this set up the same as you speak of. Are you referring to having a "front end" database and this db has an "autoexec" associated with it? Could you give me general directions on creating an "autoexec" ? Maybe this way I will be able to get the Scheduler to run correctly.....
thanks much,
sarah
