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

FORM_FATAL Built-in

Description

Returns the outcome of the action most recently performed during the current Runform session.

Outcome

Returned Value

success

FALSE

failure

FALSE

fatal error

TRUE

Use FORM_FATAL to test the outcome of a Built-in to determine further processing within any trigger. To get the correct results, you must perform the test immediately after the action executes. That is, another action should not occur prior to the test.  

Note: "Another action" includes both Built-ins and PL/SQL assignment statements. If another action occurs, FORM_FATAL may not reflect the status of the Built-in you are testing, but of the other, more recently executed action. A more accurate technique is, for example, when performing a COMMIT_FORM, to check that the SYSTEM.FORM_STATUS variable is set to 'QUERY' after the operation is done.

Syntax

FUNCTION FORM_FATAL;

Built-in Type unrestricted function

Return Type:

BOOLEAN

Enter Query Mode yes

Parameters

None.

FORM_FATAL Examples

/*

** Built-in: FORM_FATAL
** Example: Check whether the most-recently executed Built-in
** had a fatal error.
*/
BEGIN
User_Exit('Calculate_Line_Integral control.start control.stop');
/*
** If the user exit code returned a fatal error, print a
** message and stop executing this trigger.
**
** Generally it is recommended to test **
** IF NOT FORM_SUCCESS THEN ... **
** Rather than explicitly testing for FORM_FATAL
*/

IF Form_Fatal THEN
Message('Cannot calculate the Line Integral due to internal
error.');
RAISE Form_Trigger_Failure;
END IF;
END;


About evaluating the success or failure of Built-ins

FORM_SUCCESS Built-in

FORM_FAILURE Built-in