The user-defined Update, Insert, and Delete of database tables is protected through the automatic rollback provided when these instructions are forming a part of Template-based Procedures that are triggered by:

and the Abort ... switch is set to On in the Exit Inspector.

In the case of Process Procedures, the Packet object provides the necessary rollback protection, if used. The Packet provides the standard Begin Transaction, Commit Transaction, and Rollback Transaction SQL statements (the actual syntax of statements generated internally by STEP FORWARD may vary from one RDBMS to another). After dragging the Packet object into the Procedure's Workspace, the object adopts the default Begin image shown. The image shown is modified as the various DB packet options are selected.

When a Process Procedure contains a complex combination of Update, Insert, or Delete objects, then the protection afforded by the Packet object should be considered. When this feature is used, the Procedure should bracket the critical sections of the flowchart (the ones that make changes to the database tables) with BEGIN/COMMIT or BEGIN/ROLLBACK pairs, and make sure that either a COMMIT or a ROLLBACK is always executed before the procedure is exited.

Go to:
Table of Contents