11.01.2013 Views

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

Oracle Forms Developer – Form Builder Reference, Volume 1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FORM_FATAL built-in<br />

Description<br />

Returns the outcome of the action most recently performed during the current Runform session.<br />

Outcome Returned Value<br />

success FALSE<br />

failure FALSE<br />

fatal error TRUE<br />

Use FORM_FATAL to test the outcome of a built-in to determine further processing within any trigger.<br />

To get the correct results, you must perform the test immediately after the action executes. That is,<br />

another action should not occur prior to the test.<br />

Note: "Another action" includes both built-ins and PL/SQL assignment statements. If another action<br />

occurs, FORM_FATAL may not reflect the status of the built-in you are testing, but of the other, more<br />

recently executed action. A more accurate technique is, for example, when performing a<br />

COMMIT_FORM, to check that the SYSTEM.FORM_STATUS variable is set to ’QUERY’ after the<br />

operation is done.<br />

Syntax<br />

FUNCTION FORM_FATAL;<br />

Built-in Type unrestricted function<br />

Return Type:<br />

BOOLEAN<br />

Enter Query Mode yes<br />

Parameters<br />

none<br />

FORM_FATAL examples<br />

146<br />

/*<br />

** Built-in: FORM_FATAL<br />

** Example: Check whether the most-recently executed built-in<br />

** had a fatal error.<br />

*/<br />

BEGIN<br />

User_Exit(’Calculate_Line_Integral control.start<br />

control.stop’);<br />

/*<br />

** If the user exit code returned a fatal error, print a<br />

** message and stop executing this trigger.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!