B
bronco
Guest
From the help: The FINALLY block is an undoable block with implicit ON ERROR UNDO, THROW error handling, and like all blocks, FINALLY blocks implicitly throw all stop objects. You cannot explicitly override the ON ERROR directive for a FINALLY block. If a statement within the FINALLY block raises ERROR, the FINALLY block will be undone, and ERROR will be raised in the block that encloses the associated block of the FINALLY block. Error is not raised in the associated block. Otherwise, infinite looping could occur. The same is true if the FINALLY block raises STOP. Particularely: If a statement within the FINALLY block raises ERROR, the FINALLY block will be undone So I would say it's expected baviour. IMHO: raising errors in the FINALLY should be avoided at all costs. FINALLY is there for cleanup purposes. You should use a DO ON ERROR UNDO, THROW + CATCH and return the error from the CATCH block.
Continue reading...
Continue reading...