What can you do to correct this problem?

There are certain errors that are specific to the Salary item on the Employees form. You want to
trap these errors only when the user navigates from the Salary item.
You have a form-level On-Error trigger that traps errors that apply to the form in general, but yon
additionally code an item-level On-Error trigger for the Salary item.
When testing the form, you find that the general errors are not trapped when you navigate from the

Salary item. What can you do to correct this problem?

There are certain errors that are specific to the Salary item on the Employees form. You want to
trap these errors only when the user navigates from the Salary item.
You have a form-level On-Error trigger that traps errors that apply to the form in general, but yon
additionally code an item-level On-Error trigger for the Salary item.
When testing the form, you find that the general errors are not trapped when you navigate from the

Salary item. What can you do to correct this problem?

A.
Call the form level On-Error trigger from the item-level On-Error trigger.

B.
Call the item-level On-Error trigger from the form-level On-Error trigger.

C.
Change the Execution Hierarchy property for the item-level On-Error trigger.

D.
Change the Execution Hierarchy property for the form-level On-Error trigger.

E.
Move all the code to a PL/SQL program unit and call it from both the form level and item level
On-Error triggers.

Explanation:
when you have a WHEN-NEW-ITEM-INSTANCE :if you create a trigger on item,
block and form-level, then only the ITEM-Level will start. If you use the exec-hierarchy Override.If
all trigger use After, then the FORM, BLOCK and ITEM starts in that sequence.If all trigger use
Before, then the ITEM, BLOCK and FORM starts in that sequence.the execution-hierarchy on
FORM-Level is ignored, because there is no higher level than FORM



Leave a Reply 0

Your email address will not be published. Required fields are marked *