You have a form that called a database stored procedure. You do not want processing to continue, so immediately after th
Posted: Sun Jun 11, 2023 3:56 pm
You have a form that called a database stored procedure. You do not want processing to continue, so immediately after the call to the stored procedure, you add the following code:IF NOT FORM_SUCCESS THEN -MESSAGE ('Stored Procedure failure');RAISE FORM_TRIGGER_FAILURE;END IF;You test the code and input some data that intentionally causes the stored procedure to fail. However, the message that you defined does not appear. What are two possible reasons for this?
A. You must handle database errors in an exception clause of the trigger.
B. You must test for FORM_FAILURE when testing for failure of a stored procedure.
C. You must test for FORM_FATAL when testing for failure of a stored procedure.
D. FORM_SUCCESS tests for failure of Forms built-ins, not stored procedures. E. You cannot test for failure of a stored procedure, because database errors are transparent to Forms.
A. You must handle database errors in an exception clause of the trigger.
B. You must test for FORM_FAILURE when testing for failure of a stored procedure.
C. You must test for FORM_FATAL when testing for failure of a stored procedure.
D. FORM_SUCCESS tests for failure of Forms built-ins, not stored procedures. E. You cannot test for failure of a stored procedure, because database errors are transparent to Forms.