>I didn't try the TRY ... CATCH. It didn't seem like that would fix the problem. It seems like the real problem is when the error occurs within the object itself (i.e. the object's code) and calls the external error procedure. I guess to me, it seems like the try catch would still be doing the same thing ... internal error handled by an external procedure.

Are you using the .error() method of the object? Is there any code in it? You could use that to log the error and tell the object to do a harakiri, i.e. exit gracefully. Provided it's based on a class which has a .release() method, it should be able to do that.