Hi,I have a Windows 2003 server with Terminal Services. I have a couple MS Access databases which, when opened, perform a number of non-interactive tasks and then close. I have added the launch of these two databases to a Windows scheduler, to be run every night at 11:00pm even when the user is not logged in (credentials supplied).When I check the next task, that task schedulers indicates that the tasks ran successfully. But when I check the actual affected database, there is no change, so it clearly has not run.One of the tasks in the Access app is to upload data to an FTP site (process launched by Access, runs in a cmd.exe window).Is there an incompatibility somewhere that I should be aware of?raeldush

Hi Raeldush, According to your description, I understand that your Access job did not run as a scheduled task. To runs in a cmd.exe window in scheduled task, please also grant the task user account into the member of "log on as a batch job". You can follow the steps below: 1. Run "secpol.msc" to open "Local Security Policy" 2. Navigate to [Local Policies\ User Rights Assignment\ log on as a batch job] 3. Add the user account into this group. If the issue persists, please add " > jobstatus.txt" at the end of your cmd line. Then paste the jobstatus.txt here for our further research. This posting is provided "AS IS" with no warranties, and confers no rights.

Sorry for delayed response... been on holiday.Will try it out and see what happens.raeldush