Dan: It seems that something is happening inside your form. Try the following:
SET MESSAGES ON SET ERROR MESSAGES ON OUTPUT var_before.txt SHOW var OUTPUT SCREEN enter using dispatch Define an EEP for your exit button as follows: --exit_button.eep OUTPUT var_after.txt SHOW var OUTPUT SCREEN EXITFORM RETURN As an option, you can place a pushbutton with and EEP similar to the one above (minus the EXITFORM command and a different file name) in your form and click it before you exit the form, so it will dump the variables just before you exit the form. This procedure will allow you to compare the variables before entering the form (in between) and (hopefully) after exiting. The SET commands will display errors and/or messages while running the form. Hopefully you will get enough clues to find your problem. Javier, Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS 66062-4571 (913)829-0888 (913)649-2904 FAX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Sent: Tuesday, February 18, 2003 9:14 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Crashing There isn't an exit eep.... I am using the pre-defined exit on the button. It should just return me to ther calling program. (actually does 99% of the time unless I open more forms inside the form) Also, just changed it to edit using and no change. Dan At 03:53 PM 2/18/2003 +0000, you wrote: > >Dan, > >What does your "exit" eep look like? > >If your form only contains variables, have you tried "edit using" vs. >"enter" > >Ben Petersen > > >On 18 Feb 2003, at 18:28, Dan wrote: > >> >> Hmmm, >> No, I have a predefined 'exit' button on the bottom of every form for >> consistancy. I use the NOHEADER option as often as I can. >> >> >> >> >Dan: >> >Are you exiting the form by clicking the X on the corner of the form? >> >I would suggest that you run the form using the NOIHEADER option >> >
