>This is a pure SWAG, but try this in place of a QUIT statement:

>DECLARE ExitProcess IN WIN32API INTEGER uExitCode
=ExitProcess(0)

*** I'll add it, compile and send it to him.

>What, if any, ActiveX components are you using in your apps? Not just controls; do you start any out-of-process servers for your app, and is there any way to tell if they're still running after your app quits? I've seen this scenario with some poorly-conceived out-of-process servers (I should know, since I'm the one who wrote them) that died in a particularly ugly and unforgiving fashion if a second instance started on the same system.
>

*** Running the following ActiveX:
Dynazip ActiveX controls for zip and unzip.
Mabry - ras and mail controls.
M$ Monthview control.
MSACal control.

Thats it. I'll try emailing him the test quit procedure. Probably get back tomorrow.

Regards
Robert