DML Returning Value Property
Specifies whether Forms should use new or old behavior when updating client-side data with changed values after a database update or insert. A Yes setting for this property selects new behavior (new as of Release 6). A No setting selects old behavior (behavior of Release 5 and earlier).
A database update or insert action may initiate server-side triggers that cause alterations or additional changes in the data. In Release 6, when using an Oracle8 database server, Forms uses the DML Returning clause to immediately bring back any such changes. When this property is set to Yes, Forms will automatically update the client-side version of the data, and the user will not need to re-query the database to obtain the changed values.
When this property is set to No, Forms will not automatically update the client-side version of the data. (This is its pre-Release 6 behavior.) In this case, if the user subsequently tries to update a row whose values were altered on the server side, the user receives a warning message and is asked to re-query to obtain the latest values. This No setting is available as a compatibility option.
Forms automatically uses DML Returning Value for update statements when Oracle Forms is running against an Oracle database for blocks that are based on a partition table. However, this only applies to the blocks that have ROWID selected, i.e. key mode is automatic/unique. If the ENABLE ROW MOVEMENT clause is not set, Oracle Forms returns the Oracle Database error ORA-14402: updating partition key column would cause a partition change and the Forms update fails.