Frozen button after print

[Greg Fong]

In my invoicing app I have a print button sitting on my invoice form which runs a series of inventory table postings followed by a parentform.commit() before running a print operation. The printing script was scabbed off the print report action script. As for all my buttons I make sure that I have a this.disable() and a this.enable() at the beginning and end of the script.
For all intents and purposes the print preview works, I don't know about hardcopy but anyway.


The problem is that after running the script I find that several forms remain open including a few instances of the invoicing form. If I run the preview several times I get the famous "maximum stack depth exceeded" message. When I take the printing code out the system works fine. I could press the print button to my hearts content without generating extra sessions. The following is the code I scabbed:

dim A_ASK_PRINT as c
A_ASK_PRINT = ui_get_radio(this.text, 1, "Print", "Preview")
if A_ASK_PRINT = "Print"
goto print
elseif A_ASK_PRINT = "Preview"
goto preview
else
goto cleanup
end if
print:
:Report.print("invoicing",db_filter_get(db_current()),db_order_get(db_current()))
goto cleanup
preview:
:Report.preview("invoicing",db_filter_get(db_current()),db_order_get(db_current()))

goto cleanup
cleanup:
end

Is there something I am missing?

[Greg Fong]

RE: Frozen button after print

Sorry, I forgot, the button that opens the form that contains the "print" button becomes inactive as well as the button that opens it.

[Tom Cone Jr]

RE: Frozen button after print

Greg, consider the possibility that the script may not be running in strict sequential order. The postings you describe, and even the commit itself, may not be finished when the print routine begins. I don't understand this well myself. But in other situations I've occasionally seen similar things. Most often when I've included code which manipulates and saves records in several tables, and then begins another process. The code seems to keep running while other processes are off doing the file saves and related index updates...

My suggestion would be to look for a way to break your process into smaller, discrete, processes. Look for ways to defer the print routine until you know, for a fact, that the changes you need have been written to disk.

-- tom

[Greg Fong]

RE: Frozen button after print

Tom, this problem seems to be related to my other post "sessions left after report print". The problem stems from trying to print from a form based on a set that is called by a single table form containing a table that also occurs in the set. I manage to find a workaround but I can't understand why my first setup won't work.