>In my case I dont need to guess what object to get back to. I know that. I am not sure if it would have been 100% safe to jump back to that object from any failure in the program. That's my problem. It's going to be very hard to test something like this.

If instead of direct sql you would use function like RunSQL, then you would know that your select failed and would act accordingly.

Otherwise I don't see a simple way to proceed

say:

try
  myobject does something
  some select
  another select
  ...
catch to loEx
endtry

if one of the select fails, you would be trown out of the original code sequence.

Or what exactly are you talking about?