Michael,

In generaly, this is the idea behind the use of RETRY and RETURN in an errorhandler.

The problem is that it will be to tricky. If something reaches the general errorhandler it is called an "unexpected error".
Even if you can return one level back, this does not mean that this level will work. If, for example, you return one level back on a funtion with expected char and return boolean, it will fail too. This is the "cascade of techy errors"

Since nobody realy nows what will happen next, the only conclusion is to shut down the programm as safe as possible. This mean you need to call a handler that closes all data and shout the app dead.

How safe it will be depends on the application and programming style (buffering, use of transactions etc.)

Anything else would mean that the errohandler understand the prog.

BTW, yes there is a bug in RETURN TO Prog eExpression. This statement should raise an compiler error.

Agnes