Programming Guide - Actian

How You Can Use Break ConditionsFor a break on a user event, you can also edit the event's name and three ofits message parameters (messageinteger, messagevarchar, andmessagefloat). For a database event, you can edit the name or text of theevent. For window manager events, you can only use the buttons to processthe event.If the event that caused the break is part of an event chain, the message atthe top of the dialog does not necessarily name the actual event in the chainthat caused the break. To see this name, click the Break button.The buttons on the Break on Event dialog provide the following options:BreakContinues the event break execution.It displays the Debugger window positioned on the first statement in theevent block for the event that caused the break. From here, you canperform all of the Debugger functions available from the Debuggerwindow. For more information about the Debugger window, see How YouCan Debug Applications.In the case of chained events, the block on which the Debugger window ispositioned may not be the block that is named in the message on theEvent Break Conditions dialog.IgnoreSkips the event named in the dialog.If you select this option, execution continues as if the event did not occur.ContinueExecutes the event.The application does not stop until the next break condition isencountered.Error Break ConditionsAn error break condition passes control to the Debugger when the error breakthat you set occurs. You can set an error break condition for any of thefollowing error types:• All errors• DBMS errors• Data facility errors that result from such situations as data typemismatches452 Programming Guide