I have a .accdr which writes data to a text file and then closes. The application runs ok from the Windows Run Program box or if dbl-clicked. However when Visual Cron tries to run the script, whether on-demand or in a schedule I get the error above which might suggest that Visualcron does not recognise .accdr as an excecutable application. Any ideas what I might be doing wrong ? Thanks.
[ Windows 7 - 32 bit pc - Office 2010 Visual Cron 8.2.9]

What you can do is to use the "engine", in this case Access in command field. Use the full path to it. And then the full path to your accdr file in argument.

---

Sorry but this doesn't work either - I get an unhandled error - "Stdin as not been redirected". I am using the same command string and arguments which work fine with the inbuilt Windows 7 scheduler.

Sorry but this doesn't work either - I get an unhandled error - "Stdin as not been redirected". I am using the same command string and arguments which work fine with the inbuilt Windows 7 scheduler.

Please remove the StdIn selection. It is not valid here.

---

I've used the help and scanned the vast number of tabs but I can't see how to disable stdIn. Please can you provide either a screen shot or some navigation instructions. Thanks.

I've used the help and scanned the vast number of tabs but I can't see how to disable stdIn. Please can you provide either a screen shot or some navigation instructions. Thanks.

You have filled the StdIn field in the Task. Please remove the content there in the Task settings.

---

Ok, I see stdIn is the starter directory - the one where the .accdr file is located. When I remove this I get no error but the job runs for ever- stuck on 99%. The .accdr, when run directly, finishes inside 2 seconds, and the same happens with the Windows task scheduler.

I am evaluating your product to run jobs such as this for several clients so it is important that I can set them up easily. Where do we go next on this ?

Ok, I see stdIn is the starter directory - the one where the .accdr file is located. When I remove this I get no error but the job runs for ever- stuck on 99%. The .accdr, when run directly, finishes inside 2 seconds, and the same happens with the Windows task scheduler.

I am evaluating your product to run jobs such as this for several clients so it is important that I can set them up easily. Where do we go next on this ?

I think we misunderstand each other. StdIn is for very special applications that support it. In your case, I do not think standard in should be used at all. You should just use the path to the file you want to process in argument field.

---

I did understand your instructions - stdIn was empty and the path to the .accdr was in the arguments.
It seems that I also need to check the Use Shell Execute and provide credentials in Run Task as . When I do this the job runs as it should.

Thanks for your help on this.