Oracle Forms Developer – Form Builder Reference, Volume 1

Usage Notes
118
NO_ROLLBACK Form Builder exits the current form without rolling
back to a savepoint. You can leave the top level form without performing a
rollback, which means that you retain the locks across a NEW_FORM
operation. These locks can also occur when running Form Builder from an
external 3GL program. The locks remain in effect when Form Builder
returns control to the program.
Because the default parameters of EXIT_FORM are ASK_COMMIT for commit_mode and
TO_SAVEPOINT for rollback_mode, invoking EXIT_FORM without specifying any parameters in
some contexts may produce undesired results. For example, if the form is in POST only mode and
EXIT_FORM is invoked without parameters, the user will be prompted to commit the changes.
However, regardless of the user’s input at that prompt, the default rollback_mode of TO_SAVEPOINT
rolls back the changes to the form despite a message confirming that changes have been made. To avoid
conflicts explicitly specify parameters.
EXIT_FORM examples
/*
** Built-in: EXIT_FORM and POST
** Example: Leave the called form, without rolling back the
** posted changes so they may be posted and
** committed by the calling form as part of the
** same transaction.
*/
BEGIN
Post;
/*
** Form_Status should be ’QUERY’ if all records were
** successfully posted.
*/
IF :System.Form_Status ’QUERY’ THEN
Message(’An error prevented the system from posting
changes’);
RAISE Form_trigger_Failure;
END IF;
/*
** By default, Exit_Form asks to commit and performs a
** rollback to savepoint. We’ve already posted, so we do
** not need to commit, and we don’t want the posted changes
** to be rolled back.
*/
Exit_Form(NO_COMMIT, NO_ROLLBACK);
END;