Hi!

>Take a look to the SRVAny application in the Windowse Resource kit. It allows to run ANY application as a Windows NT service.

I'd like to add some words about "ANY":
1. "Some applications may terminate upon logoff, even though they were started as a service, if they don't ignore the WM_ENDSESSION message (or CTRL_LOGOFF_EVENT)." (SRVANY.EXE description)
2. "Microsoft does not currently recommend, and does not support, running Visual Basic applications as Microsoft Windows NT Services because the applications may exhibit unstable behavior when installed and run as Microsoft Windows NT Services." (Q175948)
3. "By convention, Microsoft Windows NT Services are designed to be non-interactive. That is, in most cases, they do their work without any user interaction. Services are usually configured and controlled with an applet installed in the Control Panel. This requires that the programmer add code to provide for these additional requirements:
- Report warnings and errors in the system or application logs. You typically can't use output to the screen because there may be no user logged on.
- Control the service through a separate application or through a Control Panel applet. This involves implementing a communication mechanism for your service.
- Install and remove the service from the system." (Q175948)

Therefore, an application must be specially developed to run as NT service,
and IMO nobody can garantee a (stable) work of VFP application as NT service.