Hi!

Probably this is not correct. VFP app cannot be a service, thus it is a usual APP just ran and controlled by 3-d party product. This is a usual app that system do not know if it is application or service - because ist is just a separate runnign module. Opposite to this is a VFP COM object. In the help for this function I read following:

This function intercepts Windows logoff messages (WM_QUERYENDSESSION and WM_ENDSESSION) to Visual FoxPro and specifies whether to keep Visual FoxPro COM Server instances running or to shut them down.

That means when you have a SERVICE that use VFP COM object, VFP COM object will not be destroyed during logout. This has nothing to do with usual VFP app.

HTH.

>>> What previously happened was the service would start and everything would be okay until a user logged into the system. When they logged out, the VFP service application would shutdown. SYS(2340) intercepts the logoff message and depending on the setting, ignores it so your application continues to run. It will still terminate if a shutdown message is detected, but only then. <<
>
>Exactly the way I was thinking about it as well. The only problem is I wrote a sample form in the Init of the form I called the SYS(2340,1). No problems ran the form had it running and logged out. The QueryUnload Event did not fire, but the program was released from memory. I know the current app was not a service, but VFP should not have ended the app.