L
Laura Stern
Guest
I'm a little confused. The only way an object is thrown out of a procedure is if you explicitly do RETURN ERROR or if your top level .p has a ROUTINE-LEVEL ON ERROR UNDO, THROW statement at the top. i.e., This cannot happen by accident - i.e., because you forgot a CATCH block somewhere or something. It has to be done on purpose, explicitly. Seems like you should be able to find this and fix it. But having said that, I agree that if you get that error (14438), we should also log the error message that caused that to happen. You could log a bug for that if it is not happening. I don't think there is anything other than using the LOG-MANAGER that you can use to turn logging on/off in the middle of a session.
Continue reading...
Continue reading...