Oracle Update Flag SOLVED

Question

I have a PRE-UPDATE trigger used for cascade updates which warns users how many tables they will be effecting when they make their changes.
DECLARE
  v_seq_num         NUMBER;
  v_tab_num         NUMBER;
  v_old_mfcode  VARCHAR2(8);
  v_new_mfcode  VARCHAR2(8);
BEGIN
v_old_mfcode := get_item_property('DD_MATFUEL.MFCODE',database_value);
v_new_mfcode := :DD_MATFUEL.MFCODE;
if v_old_mfcode <> v_new_mfcode then
SELECT COUNT(*)
INTO v_seq_num
FROM DD_MATFUELSEQ
WHERE MFCODE = v_old_mfcode;
SELECT COUNT(*)
INTO v_tab_num
FROM DD_TAB_MFCOLLAPSE
WHERE MFCODE = v_old_mfcode;     
msg_confirm ('Warning...', v_old_mfcode || ' will be updated to ' || v_new_mfcode || ' on the following tables...'||chr(10) ||
                      'DD_MATFUELSEQ ' || v_seq_num || ' instances' || chr(10) ||
                      'DD_TAB_MFCOLLAPSE ' || v_tab_num || ' instances');
end if;
END;---------------------------------------------------------------------------
On the msg_confirm() they have an option for yes or cancel. I was wondering if there was a hidden oracle forms update flag that gets assigned to rows when something has been changed. Since cancel does a rollback it is stopping all the ones they already clicked 'yes' for to rollback as well. I was hoping I could maybe put this in a loop with a commit after each check instead of using a PRE-UPDATE trigger. Any help would be appreicated.
Thanks
Message was edited by:
Yachera

Answer 1

You can create your own hidden non-base-table flag in the record, and set it depending on which button of your alert the user presses.
Then, in the on-update trigger, if they want to proceed, you can issue an Update_Record; statement, or bypass the Update_Record;
Either way, be sure to clear the flag in the on-update trigger.
But I would do all this checking in the when-validate-record trigger, or even sooner, in the On-Lock trigger, so it is processed sooner.
If you use when-validate-record, they will get the message as soon as they leave the record and navigate to the next. If they wish to cancel updating that row, you should set all the values back to their original (use Get_Item_Property(...,Database_Value), and set the record status back to Query_Status.
But even better would be in the On-Lock trigger. Check the counts and issue the alert BEFORE you issue the standard Lock_Record; command. If they want to cancel changes, all you need to do is issue a Raise Form_trigger_failure; and Forms will change the data back to original values. If they want to proceed with changes, then issue the Lock_Record; command.
Doing either of the above will prevent Forms from even trying to update the row when the user wants to save, and visually, the user can see their changes were backed out.