I have a rather simple input form which, after a certain field is completed, I ask the program (through an "ondepart" event) to save (parentform.commit()) the record. I get the following error: "Maximum stack depth exceeded." The form, however, appears to be saved. If, before exiting the field, I save the form using a "Save" button which I also placed on the form (containing the same command), it saves fine (but when I exit the field, I get the error). What does "Maximum stack depth exceeded" mean and why is the program doing this to me.
-
-
RE: Maximum Stack Depth Exceeded??
Had the same problem. Scroll down to message 18235 (March 28th I think)for problem description and solution. -
RE: Maximum Stack Depth Exceeded??
here is the message that ed was referring to:
------------------------------------
Maximum Stack Depth Exceeded� Error Message
The error occurs because the script is invoked a second time before the current instance of the script has finished executing.
The following technique in Xbasic should eliminate the error message by preventing the script from executing while a previous instance of the script is still running.
dim shared busy as L 'declare a shared logical variable
if .not. busy then 'don�t execute the script if previous instance still running
busy = .t.
'put the xbasic commands that you want to execute here
busy = .f.
end if
For example:
dim shared busy as L
if .not. busy then
busy = .t.
parentform.fetch_next()
busy = .f.
end ifComment
-
RE: Maximum Stack Depth Exceeded??
Most likely the parentform.commit() is making the OnDepart event fire again for that field. So you wind up in an endless cycle which is only terminated when A5 runs out of memory.
You can try adding a dummy button to the form and make the dummy button the last object in the tab order. Then try putting parent.commit() on the OnArrive event for that button. That might work, although it may also cause the OnArrive event to keep firing.Comment
-
RE: Maximum Stack Depth Exceeded??
I put parent.commit() on the OnDepart event of a form and it did not cause any problem. Do you have other code that is interfering with tthe OnDepart or with the commit()?Comment
-
RE: Maximum Stack Depth Exceeded??
I did have a 'parent.commit()' inside of the onsave event, so I'm pretty sure that that was the problem. I'm not getting the "exceeded" error, but I seem to have created a new one.
For some reason, after the save, the screen jumps back to the previous record. (I fire a "save" after the (lastname, firstname and) middle intial has been entered. I figure that a save of the data is inevitable and I want to populate the remaining fields on the form (but which are in a different table) with default data. I have determined that the best way to do this is to generate a child record and save the whole shebang out. But after the child record is created and the parent and child records are saved via the parent.commit(), the resulting screen jumps back a full record. And a fetch_last() won't bring it to the next (the just saved ,new, record).
I checked the mode (via trace.writeln(str(mode()))to see if somehow I'm still in enter or change mode as the record goes backwards, (which would keep fetch_next/last() from working) but I'm not. Any ideas on what could be causing this strange behavior? (Is my description clear as to what is happening?)Comment
-
RE: Maximum Stack Depth Exceeded??
How many one to many's do you have in the set?Comment
-
RE: Maximum Stack Depth Exceeded??
None. That's why is is really confusing.Comment
Comment