L
Laura Stern
Guest
Well, there may be a knowledge base on it. But that doesn't explain it. This is a bug in my opinion. A CATCH block for Progress.Lang.Error should catch the error. Many handle methods do generate warnings (not errors), but when using structured error handling that should not happen. Any error that generates an error message should get caught. If you just want to know which line is causing the error, turn on debug-alert (-debugalert or SESSION
EBUG-ALERT = yes). When the error comes up, click on the Help button to see the stack trace.
Continue reading...
EBUG-ALERT = yes). When the error comes up, click on the Help button to see the stack trace.Continue reading...