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 and use a push button with an EEP to exit the form. The advantage of this approach is that it allows you to do whatever housekeeping you need to do when exiting the form, also, you can dump the variables to a file/printer for debugging. Also, if you are running on a network, it is possible that each user is reading his/her rbase.cfg file and the files setting may not be 30 for all users. I run into this problem before (I use 50 for files by the way) and it took me a while to figure out what was happening. 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 7:51 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Crashing > I was mostly alarmed that you said you had a couple hundred variables >declared and active at one time.... I am calling a dipatching form for 10 technicians over a 12 hour period. Each period is represnted by a clickable variable (which calls another form to edit that appt) So there are 120 variable just there. There are another 40 variables displaying things like how many invoices are not turned in yet for each tech, How many calls he has to return to, etc... This main dispatch form has roughly 200 variables a01-a12 to I01 -I12 in appt boock format. This has been working for us for 3 years now, and only recently (after one of the patches) that it fails when exiting this form. Hitting the exit button does not bring be back to the calling program. I thought maybe it was having my files set too low, but files 30 doesn't change it. With all the code, and trace and whatnot, the trouble lies after the enter line, and before the pause line. (I added that to see if it just didn't know where to return to.) enter using dispatch pause 2 using "you made it back" return Granted this only fails when I have gone a few forms deeper from the dispatch form. As long as I stay in the dispatch form and keep calling eeps, it continues to work. But if I hit the exit button, then, I am tossed to the prompt instead of the calling program. Am I making sense? In tracing the Main.apx that calls the Dispatch module, I can never trace it all the way to the line where I am comming back out of the dispatch form. By the time I get there, trace has quit, and I am just running as though trace was off. Facts: A, RCode and RStyle are used religiously, B. Database unloaded and reloaded weekly. I have tested the variables present in a normal exit from this code, to the ones that exist after an abnormal exit. All the types are correct, and things seem as they should. I am sure I am missing something here, but don't know where to turn next. Trace should go that far? That would be best if I could get it to do that. Dan
