L
Laura Stern
Guest
Just an FYI; it may not alter the essentials of what you said. I really can’t think of an error that does not implement the Progress.Lang.Error interface. ProErrors certainly do. Anyway, I don’t believe you can ever actually get a ProError itself. That is an artificial level in the class hierarchy to distinguish from a .NET Exception, and even .NET exceptions implement the Progress.Lang.Error interface. I’d rather not wade through all the text above to see, and I can’t search right now (at home on my iPad), but I don’t remember you talking about Stop conditions. If so, sorry for redundancy. And if not SORRY I did not think of this till JUST now. If your version is pre 11.7 (I don’t remember if you said that either) or are using some 11.7 version, but not using -catchStop 1, then Stop conditions will not be caught by a CATCH for Progress.Lang.Error. So if you are as diligent about using structured error handling as you say, I would guess that you are getting a STOP condition. If you are using 11.7.x I would suggest using -catchStop 1 to see if that helps. Also, what error message(s) are you getting? We could probably determine if these are conditions that would generate Stop.
Continue reading...
Continue reading...