Going 10+ levels deep would make me nervous... but that's more superstitious than scientific.
I have had forms that crashed on exit... almost always while developing a new routine. Putting a "pause for 1" immediately after the edit statement helped. But, after a while, I've been able to remove (I think) all of them. Same circumstance in that trace never found a problem. I've come to believe that I had done something screwy some time before in another part of the program that set up the situation, that I later cleaned up (unknowingly). But, again, just superstition. Javier's "Quit to" suggestion is a good one. Scour the eeps that call the child forms. And, if you can, keep a log of what you do all day in the system to see if you can narrow down the circumstance that causes the problem. Trying to remember what you did 5-10 steps before a crash rarely works. Ben Petersen On 18 Feb 2003, at 21:57, Dan wrote: > > Even though this has begun happening since one of the last two patches > was installed, I dont think it is a bug other than in my own > programming somewhere. Something sloppy I did or something. The form > itself is the form that stays open almost all day and most of our > dispatching is done as a result of clicking on one of the fields and > subsequently opening further forms...(sometimes as many as 10 more > levels deep) This form only fails after certain moves are made then an > attempt is made to exit the form. It is only exiting the form that > there is trouble, That is where I am confused. The calling program > has the lines (amidst hundreds of others) > > enter using dispatch > pause 2 using "test" > return > > When all goes right, the pause comes up, and then it continues to the > appropriate calling program. When it doesn't, it closes the form, but > doesn't even do the pause. As though it doesn't even know what > program called it. > > I would never be able to send enough of the form, program, etc to RBTI > to get them to be able to replicate it. I will have to just keep > digging. > > Any other ideas on how to get trace to go far enough to get to the > problem? Or, what would stop trace from getting there? > > Dan > > > At 06:19 PM 2/18/2003 +0000, you wrote: > > > >If this issue is the result of the latest patch you should contact > >RBTI. One last possibility is that your form is corrupt... you might > >try deleting it and loading a fresh copy from a back-up. > > > >Ben > > > >On 18 Feb 2003, at 20:13, Dan wrote: > > > >> > >> Ben, > >> I changed the predefined exit button to use a custom eep, using > >> the > >> closewindow command. > >> It behaves the same as before. > >> Javier, > >> I have checked every variable before the exit, and after the exit > >> (actually this was where I started looking this morning, assuming I > >> was probably having a variable type problem) Other than sqlstate, > >> nothing is different. Dan > >> > >> > >> At 05:10 PM 2/18/2003 +0000, you wrote: > >> > > >> >As an alternative, try a custom eep using "CloseWindow". It's a > >> >shot in the dark, but I have a foggy recollection of problems with > >> >some pre-defined eeps. > >> > > >> >Thanks, > >> > > >> >Ben > >> > > >> > > >> >On 18 Feb 2003, at 19:14, Dan wrote: > >> > > >> >> > >> >> 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 > >> >> >> > >> >> > > >> >> > >> > > >> > > >
