>>That's brilliant, thanks. You are right thought just being able to say which level back you want to go to would be perfect rather than having to parse the procedure name out.
>
>I'd avoid this like the plague - you're blowing the call stack and one or more execution stacks out without being aware of the consequences of them. It's an open invitation to having dangling object refs left lying about, since there may be methods bypassed by RETURN TO that never terminate, and since the code in them is active, you'll likely not be able to release the objects involved (and their parent containers, etc.) at a later point.

Ed,

If I shouldn't do this this way how can I just Release this class ie stop it in its tracks but get it to clean up properly?