>>>>>>I am running the task (Run As) with my own account; the same account when I log on locally.
>>>>>>That's why it's so weird.
>>>>>>Do you have other suggestions?
>>>>>>
>>>>>
>>>>>I don't think you'll be able to "runas" your own account. Once you logoff, the Scheduler doesn't seem to be able to run things. I've usually set up a separate account for the app to run under or use the administrator account for simplicity. YMMV as to what should work best for you.
>>>>
>>>>
>>>>Been there, done that.
>>>>Unfortunately I tried all the things you mentioned. I even used the administrator account.
>>>>Still not working.
>>>>It looks like nobody can get to the runtime of Fox7 when there is nobody logged on locally.
>>>>We use the taskschedular on several machines and never had any problems.
>>>
>>>Try putting the runtime files in the same folder as the app.
>>
>>
>>I didn't tried that before. Good idea but...still not working.
>>I also reinstalled the fox7 runtimes but that wasn't the fix either.
>
>When you installed the runtimes, were you logged on as Administrator?

Not as user "Administator" but with my own accountname which is in the administrators group.
I first unregservered the runtime dll's (vfp7t.dll and vfp7r.dll). Then I tried to run my test script. That gave an error 'cause the runtime wasn't available.
After that I installed the runtimes (setup made with Installshield Express, just checked foxpro7 runtimes) and tried the script again. Now the script had no errors. But then I was still logged on localy. Then logged out and started the scheduled task. Looked in the logfile and the message "cannot create object" reappeared.