A script-enabled browser is required for this page to function properly.

Handling Errors in Built-in Subprograms

When a Built-in subprogram fails or causes a fatal error, you might want to direct the trigger from which the subprogram was called to fail, rather than allowing Oracle Forms to continue processing subsequent trigger statements.

In a previous topic, you saw that a trigger fails when it raises an unhandled exception. However, because errors in Built-in subprograms do not raise exceptions, you must raise an exception explicitly in your code to cause a trigger to fail:

/* When-Button-Pressed Trigger: */
Go_Block('xyz_block');
 IF NOT Form_Success THEN
  RAISE Form_Trigger_Failure;
 END IF; END IF;

Because this trigger does not have an exception handling section, raising an exception causes the trigger to fail, and Oracle Forms performs the post-failure processing appropriate for the trigger. Although any valid exception can be raised to cause a trigger to fail, the example uses the Built-in exception FORM_TRIGGER_FAILURE.


About using PL/SQL exception handling in triggers

About trigger failure results

About handling exceptions raised in triggers

About evaluating the success or failure of Built-ins

Handling errors in user-named triggers

Error handling for stored procedures

User-defined exceptions