L
Laura Stern
Guest
I don't know what you mean by "does it behave the same way when just returning a literal string". if you return an error object instance, it needs to be a class that implements Progress.Lang.Error and it needs to be SERIALIZABLE (which all the system classes are). That's the same as with UNDO, THROW. If you just return a literal string, you can catch it on the client as an AppObject where the ReturnValue property will be set to that string value. Or you can just handle the error the non-structured error-handling way (with DO ON STOP, or whatever), and the RETURN-VALUE function will return that string.
Continue reading...
Continue reading...