Thank you for your input.
>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).
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
