L
Laura Stern
Guest
Any error can be "handled" by simply displaying the error message. So there is nothing harmful about CATCHing errors that you have no further handling to do other than that. And yes, if you don't CATCH it, that is what will happen anyway (i.e., the message gets displayed). But this whole discussion started by the fact that since you are using Open Client and you cannot throw an error back to the .NET client, you need to make sure that all errors are CAUGHT at the top level so you can do your RETURN ERROR logic. You can never guarantee that a system error will not happen. Unexpected things DO happen. So that is why you should be catching Progress.Lang.Error, at least in the top level procedures on the server. And without that, the runtime/framework is "picking up the ball" and behaving exactly as documented. Though I think we already both agree that the AVM should also log the original error message when you get the 14438 message. But to avoid that message altogether, you should just be catching Progress.Lang.Error objects.
Continue reading...
Continue reading...