Forum Post: Re: Structured Error Handling In Triggers Confusion

  • Thread starter Thread starter Mike Fechner
  • Start date Start date
Status
Not open for further replies.
M

Mike Fechner

Guest
It's best practice to have a default CATCH block at the end of each UI event handler (trigger). Ours looks like this here. ErrorHelper:ShowErrorMessage show as the error in a nice dialog, with all relevant session info (from client and AppServer) and in 11.6 all properties that a custom error class may have (using reflection). If you don't show the error nicely, the AVM does it in the good, old, ugly error message box. Also be aware, that the Custom error dialog might also handle AppErrors with only a ReturnValue, but no message (UNDO, THROW NEW AppError ("This is a return value") vs. UNDO, THROW NEW AppError ("This is a message", 0). CATCH err AS Progress.Lang.Error: Consultingwerk.Util.ErrorHelper:ShowErrorMessage (err). END CATCH.

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