[progress Communities] [progress Openedge Abl] Forum Post: Re: Abl Unhandled Exceptions, Or...

  • Thread starter Thread starter slacroixak
  • Start date Start date
Status
Not open for further replies.
S

slacroixak

Guest
I has tried to use a ON STOP, UNDO, RETRY without success: DO ON ERROR UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK ON END-KEY UNDO MAIN-BLOCK, LEAVE MAIN-BLOCK ON STOP UNDO, RETRY: Tools:QuitIfInStopRestart(). IF RETRY THEN DO: MESSAGE "RETRY case" SKIP tools:GetAblErrorDetails("withCallStack") VIEW-AS ALERT-BOX. LEAVE. END. => a button Choose trigger tries to run a NonExisting.p Then I thought the ON STOP Phrase was Not working because error 293 was firing an untrap-able condition. Still my point is was to detect a STOP has occurred, which I can now do with the incremented static variable, but I am still missing the details of the error message (the name of the missing .p file)

Continue reading...
 
Status
Not open for further replies.
Back
Top