RUN_EVENT line 1... (None Specified)
At 03 OCT 1998 09:50:17PM Donald Bakke wrote:
Does anybody remember what causes this error:
RUN_EVENT line 1: the labeled common variable has been freed and is no longer valid.
Any quick ideas would be greatly appreciated.
dbakke@srpcs.com
At 04 OCT 1998 02:11AM Andrew McAuley wrote:
[notag]Normally sending a close event in an event handler then continuing processing instead of abort alling.
[<A HREF="mailto:amcauley@sprezzatura.com" onMouseOver="window.status='Why not click here to send me Email?';return(true)">Andrew McAuley</A>]
[<A HREF="http://www.sprezzatura.com" onMouseOver="window.status='Why not click here to visit our web site?';return(true)">Sprezzatura Ltd</A>]
[<I>World Leaders in all things RevSoft</I>]
[<img src="http://www.sprezzatura.com/zz.gif">]
[<HEAD>]
[<script language="javascript">function openNewPage (){window.location.href=(document.TOCNavigator.pageToGoTo.options[document.TOCNavigator.pageToGoTo.selectedIndex].value);document.TOCNavigator.pageToGoTo.selectedIndex="0";}end hiding from non-JS browsers–></script>] [</HEAD>] [<FORM ACTION "" METHOD=GET NAME="TOCNavigator" <SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()"> <OPTION>Pull down this menu to choose whereabouts on Sprezz site to go <OPTION VALUE="http://www.sprezzatura.com">Home Page <OPTION VALUE="http://www.sprezzatura.com/whatsnew.htm">What's New <OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL <OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST <OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura <OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura </SELECT> </FORM>][/notag] </QUOTE> —- === At 04 OCT 1998 06:27PM Donald Bakke wrote: === <QUOTE>Hi Andrew, Thanks for that reminder. I haven't gone back into the code yet, but I know that a CLOSE event is being sent to the active window in the midst of a LOSTFOCUS event from a control on the same form. So this seems likely to be the case. I searched this discussion base for other references to ABORT ALL and saw where you had responded before on this issue. You gave credit to some original RevSoft programmers for this tip. But this leads me to a couple of questions I'd like to bounce off of you (and anybody else who can contribute): 1. Is ABORT ALL really a proper way to go? I understand why an error in RUN_EVENT can occur. When you think about it, it seems odd to expect an event for a window/control that no longer exists to continue properly, so this makes sense. Therefore, shouldn't we be in the practice of redesigning our code to conform to a logical pattern rather than cram in an ABORT ALL statement? 2. Doesn't ABORT ALL basically cease all currently running code, therefore making any code that occurs after the CLOSE event useless? Consequently, this makes my suggestion in #1 all the more meaningful. I may be misunderstanding how ABORT ALL works but it still seems about as elegant as placing STOP's everywhere in AREV code whenever one wanted to end a routine. Thanks for your input. dbakke@srpcs.com SRP Computer Solutions
[</HEAD>]
[<FORM ACTION "" METHOD=GET NAME="TOCNavigator"
<SELECT NAME="pageToGoTo" SIZE=1 onChange="openNewPage()">
<OPTION>Pull down this menu to choose whereabouts on Sprezz site to go
<OPTION VALUE="http://www.sprezzatura.com">Home Page
<OPTION VALUE="http://www.sprezzatura.com/whatsnew.htm">What's New
<OPTION VALUE="http://www.sprezzatura.com/senl.htm">SENL
<OPTION VALUE="http://www.sprezzatura.com/patches.htm">Download S/LIST
<OPTION VALUE="mailto:support@sprezzatura.com">Send mail to support at Sprezzatura
<OPTION VALUE="mailto:sales@sprezzatura.com">Send mail to sales at Sprezzatura
</SELECT>
</FORM>][/notag]
At 04 OCT 1998 10:15PM Donald Bakke wrote:
Follow up…
This was the problem and ABORT ALL did fix it, so to speak, but it also prevents ALL remaining code from executing, including any calling routines.
Therefore, POST_EVENTing or setting a flag so the SEND_EVENT can occur at the very end is the better way to go.
Thanks again,
dbakke@srpcs.com
At 05 OCT 1998 01:36PM DSig (SigSolutions) wrote:
Don,
I have seen this when an event has processed and is called again.
For example .. in the write event you want to close a screen automatically on write for specific responses. So you forward the event then send_event close. But if the user click on system close .. the close event would call the write event would call the close event and BANG ..
DSig
David Tod Sigafoos ~ SigSolutions
dsig@teleport.com