Armin, another thing I did with the C++ side was add a routine that will impersonate a User when starting the service. This way that service will have access to network resources like SQl Server. The user types this info into a VFP frontend that just writes to the registry. The C++ reads that info from the registry when it starts the service. To the end user, this is all very smooth and no manual config of the service or registry is necessary...
>Claude,
>
>>Thanks for trying.
>
>No problem!
>
>>I did the same as you and wrote a VB wrapper for VFP a while back that will start a VFP exe as a service.
>
>Yes, this way you can start/stop the service. If you want to have more control (Pause/Continue/Custom actions) you could also think of making a COM DLL out of your VFP EXE and just pass the SCM messages through the VB EXE to the VFP COM DLL as method calls. This way you can have it all :)
>
>>I think the problem in VFP is that the C++ service controller part is working with 2 threads of VB which probably can't be duplicated in VFP...
>
>Yeah, this might be the problem, but I have to admit, that my knowledge about these things is really limited.
>
>Armin