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

Post-Change Trigger

Description

Fires when any of the following conditions exist:

Definition Level form, block, or item

Legal Commands

SELECT statements, unrestricted Built-ins

Enter Query Mode no

Usage Notes

The Post-Change trigger is included only for compatibility with previous versions of Oracle Forms. Its use is not recommended in new applications.

The Post-Query trigger does not have the restrictions of the Post-Change trigger. You can use Post-Query to make changes to the fetched database values. Given such changes, Oracle Forms marks the corresponding items and records as changed.

On Failure

If fired as part of validation initiated by navigation, navigation fails, and the focus remains in the original item.

During fetch processing, Post-Change triggers defined as PL/SQL triggers do not operate with these restrictions. During a record fetch, Oracle Forms does not perform validation checks, but marks the record and its items as Valid, after firing the Post-Change trigger for each item.

Fires In

Validate the Item

Fetch Records

Post-Change Trigger Restrictions

Note that it is possible to write a Post-Change trigger that changes the value of an item that Oracle Forms is validating. If validation succeeds, Oracle Forms marks the changed item as Valid and does not re-validate it. While this behavior is necessary to avoid validation loops, it does allow you to commit an invalid value to the database.


Post-Query Trigger