If ever you need a service, best to create it with NET instead. This is much easier and creates its own installer.

Even then, if the service is crucial, create a second service to watch the service activity and restart on demand. In the latter case it could then work with a VFP application for the main service if it has to be.

>Thank you. Then the windows scheduler will be the approach (if customer approves, of course).
>
>>Been there, done that. I would second on Sergey's advice. Do not try to run a VFP service with a timer continuously. It stops working with no reason. We ended up with using windows scheduler itself (also much more flexible).