Paul, A couple of suggestions:
1) Put a RETURN after your EXIT. All command code should always end with EXIT. 2) Rather than fool around with creating temp folders and deleting $$$ files, why not just: SET SCRATCH TEMP -or- SET SCRATCH TMP Let R:BASE use the folder defined in the user's environment, and trust it to manage the deletion of the $$$ files. The latest 7.6 version does a good job of this, if you let it. I'd reduce your code to this: PROPERTY application TITLE 'Name of Company' SET SCRATCH tmp CONNECT NdbName SET QUOTES=' SET MANY=% SET SINGLE=_ EDIT USING someform EXIT RETURN I also took out the DISConnect; it isn't necessary, but doesn't do any harm. Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Paul InterlockInfo Sent: Friday, October 31, 2008 3:40 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Compiled App is still running? I have a simple form that has time, date and client information (I will leave all that out for now, it does not apply) this form is activated by the following command: PROPERTY application TITLE 'Name of Company' CLEAR VAR vchkfile SET VAR vchkfile INTEGER = NULL SET VAR vchkfile = (CHKFILE('C:\TEMP')) SET VAR vtimerstart TIME = (.#TIME) IF vchkfile <> 1 THEN MKDIR c:\temp ENDIF SET SCRATCH c:\temp SET ERROR MESSAGE 2262 OFF SET ERROR MESSAGE 2926 OFF SET ERROR MESSAGE 2077 OFF ERASE c:\temp\*.$$$ SET ERROR MESSAGE 2926 ON SET ERROR MESSAGE 2262 ON SET ERROR MESSAGE 2077 ON CONNECT NdbName SET QUOTES=' SET MANY=% SET SINGLE=_ EDIT USING someform DISCONNECT NdbName SET ERROR MESSAGE 2262 OFF SET ERROR MESSAGE 2926 OFF SET ERROR MESSAGE 2077 OFF ERASE c:\temp\*.$$$ SET ERROR MESSAGE 2926 ON SET ERROR MESSAGE 2262 ON SET ERROR MESSAGE 2077 ON EXIT --Note**(I even add Exit twice here just in case and also tried "Return" instead of "Exit" same great results) When I compiled this code and run it - then "EXIT". I can go to the task manager and see it still there. Now it is not really running, but taking up a PID. I went in (Task Manager) and I do not see any dll's and/or handles running with this app/exe. (Ok, I used something like Task Manager but a bit more in depth.) If I open another session or many be several they all line up in a row (In task manager). I can stop the process and hope I select the correct one. As an extra note * No before or After EEP's rather older form, no special code or calls. I mention this because I only open the form and Exit for this test now. I traced this run_command.dat and when it hit the "Exit" the process "RBG76EE.EXE" quickly was removed from Task Manager. Sincerely, Paul Dewey
