S
Stefan Drissen
Guest
Yes, that part is clear. But what about cleaning up any mess? The top level procedure has no, and wants no, idea of the work that has been done at lower levels. How does it know what it needs to clean up? In the case of dynamic objects these could be dumped into (named) widget pools or deleted by walking the dynamic object handles. But what about a persistent super that has errored out with a duplicate (no-undo) static temp-table record? Any subsequent hit to that super will persistently keep erroring since it has nowhere to put the duplicate. Maybe persistent supers need more care and need to catch and cleanup their own messes?
Continue reading...
Continue reading...