Why not compile your application in a EXE and run that EXE from the scheduler?

The job run as a normal process, if the network drive are mapped then the application will see them. However, you should stay away from mapped drive and use the full network path IMHO (\\ServerName\Drive\...)

You can store the output of the batch process in a table, file, as a Windows event, by email, etc. depending on your needs.

>Hi all. I am humbly seeking help with questions about running a VFP8 app as a scheduled task.
>
>In our particular situation, which involves kind a mixed development / deployment environment, it would be preferable to have a batch job fire up VFP on schedule (e.g., runtime VFP8R.exe) and point it to an FXP.
>
>What I'm not clear on is how to create an appropriate run-time environment for the process. For example:
>
>- The job runs as kind of a detached process, no? So if a mapped network drive needs to be accessed by the app, how to make the drive available? Should I use a BAT file and first put a NET USE command in it before the VFP8R command?
>
>- Along those lines, I believe it is true that the log-on identity of the task can be specified with the "run as" feature within the task scheduler. If the "run as" identity I specify has already indicated (in the past, interactively) that a network drive should be mapped at log in, then is explicit mapping unnecessary within the Bat file?
>
>- What is "standard output" for such a task? What is the best way to capture output from an FXP that is running within a batch job?
>
>Any other suggestions / pitfalls to be aware of?