[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== Exit Debug back to Form Designer (OpenInsight Specific) ====
=== At 22 SEP 1999 11:45:49AM Dale  Walker wrote: ===
 
{{tag>"OpenInsight Specific"}}
 
<QUOTE>
Having created a test form in form designer based on Arev 3.12, I click on the test icon and then enter a date (key field) and then because of a default routine for the next field that isn't up to snuff, the debugger activates as it should. I understand the message given but I want to go back to the form designer and so I click on file, exit and then the debugger reactivates for the same field and then appears to be caught in a loop. 



I am using OI3.5.



Is there any way to exit without having to ctrl-alt-del and then reboot the system (NT) because the engine wont run when I click on the OI icon?



Dale
</QUOTE>
----

=== At 22 SEP 1999 11:58AM Stephen S. Revelation wrote:  ===

<QUOTE>Dale,



From within Debugger, if you choose the Run menu option you may 'Go then Disable (Debugger)' or 'Abort then Disable'.  To re-enable Debugger, from Application Manager choose Tools-]Database Manager-]Database-]Environment Settings then choose the 'Enable Debugger' checkbox.



I hope this is what you were looking for.



-Stephen

</QUOTE>

----

=== At 22 SEP 1999 12:21PM CT Savell wrote:  ===

<QUOTE>Your response included: "To re-enable Debugger, from Application Manager choose Tools-]Database Manager-]Database-]Environment Settings then choose the 'Enable Debugger' checkbox."



I appreciate your sharing this information as I have continuously had to exit OI and reenter to reenable the debugger.  I feel hiding the "reenable debugger" feature in an obscure corner like this is a bad design practice on Revelations part.  "Reenable debugger" should be (also) in the Form Designer menu options, perhaps under tools.

</QUOTE>

----

=== At 22 SEP 1999 01:06PM Dale Walker wrote:  ===

<QUOTE>Yes it was what I was looking for. 



However, wouldn't it be simpler to have the box that pops up and gives the message have a box that asks: "exit Debugger?" with button options?



This way, there would be less frustrations to new, intermediate, and old users.



Dale

</QUOTE>

----

=== At 22 SEP 1999 01:58PM Stephen S. Revelation wrote:  ===

<QUOTE>CT,



Well, actually, another way to re-enable Debugger [i]is[/i] to go to Tools.  Tools-]Advanced-]Debugger.  This brings you into Debugger, which is activated, simply by being accessed.  You may re-[i]dis[/i]able it onces again by the same "Abort then disable", etc. again or just exit Debugger, now enabled.



-Stephen

</QUOTE>

----

=== At 22 SEP 1999 02:34PM CT Savell wrote:  ===

<QUOTE>OK, that's cool.  Now I have two approaches.  If I understanding it correctly, the second one sounds a little simpler, but...



However, neither is as user friendly or as obvious as having something right in form designer. The "Run-man" test button is great, very friendly until you get stuck in a loop and you have to abort and disable to get out.  I can do that within the Form Designer.  I should be able to reenable without having to leave Form Designer as well.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=5AD8276E7E0E5E38852567F4005697BD|View this thread on the  forum...]]