>I would write a bullet proof with serious error logging FoxPro EXE that has no UI and doesn't use a Timer and have it run as a Windows scheduled task every x minutes.

>The Windows Scheduler logs the start of the task and is easier, IMO, to maintain and configure. I've used Windows Scheduler a lot and it works fine. You just have to write a very smart program that cannot fail without writing out an error log.

>Whether a Service can run a VFP EXE with a Form is something that I doubt can happen, but I don't know for sure.
>And in the past I've had trouble with FoxPro Timers where they don't fire.

100% agree, especially about timers not being reliable.
The other thing that will earn trouble is file operations to networked machines.
It is better to only work with files local to the machine where you schedule the task.
If you must go across the network, use UNC names, NOT mapped drives.