Help : commit processing

Question

Hello,
I want to change the commit precosess, so
when forms will save items into database,
I want it to skip one item and do not save it even if it has receive a value!!!!!!
I think that I have to use a key-commit trigger,
but how can I prevent the comit of the item!!!
Thanks for help

Answer 1

Ino, Steve
I agree with both of you.
Jina
(1) Your first question was
I want forms to commit this item when it's value is :X
and do not when it's != X!!!This means you didn’t want forms to commit only this particular item. There was no mention about the database trigger there !!! Meaning you had issue only with commit of that particular item.
(2) Your second statement was
I don't want want forms to take consideration of this item
when commit processing is done because I have a database trigger that I don't want it to >execute when the value of this item ='X'When you say "you don’t want forms to take consideration of this item when commit processing is done" it means that you want form to ignore the item and not commit it but at the same time commit others.
Is your issue the firing of trigger or the commit of that particular item or BOTH ??
(3) Anyway this is my understanding of your issue :
(a) If you are accessing the table from your forms application and the value of a particular item is 'X' then you don’t want the database trigger on that table to fire at all.
(b) If you are accessing the table from your forms application and the value is !='X' then the normal processing should continue and the database trigger should fire as usual.
(c) If you are accessing the table from any other applications, irrespective of value of that item, the normal processing should continue and the database trigger should fire as usual.
Assuming your database trigger fires before insert or update on that table, and above conditions (a),(b),(c) are true, then you could create an extra column in the base table which acts like a flag. You could set the flag column value to lets say 1 from your forms application. Set it to lets say 2 from other applications.
In the trigger solution given by Ino you could make following changes
IF :new.flag = 1 AND :new.item = 'X' THEN
-- no changes. The trigger shall still be fired, but whatever code in the trigger shall not execute.
NULL;
ELSE
-- do something ... Whatever you want the trigger to do
END IF;
REMEMBER here that if that item is a database table item then it shall still be committed, with whatever value it holds, like the other items. If you don’t want the item to commit, Ino gave you the solution. Make it a non-database item. Then if the value is correct and you want to commit the item, in pre-insert trigger assign the value to a non-display item that represents the database column. If the column is non mandatory and the application does not supply any value for it, then
(1) The column's default value as specified when the table was created is inserted or updated
(2) If no default value was specified, then a null value.
If your database trigger is different, then the solution might differ. In that case post a reply along with the database trigger.
Regards
Poorvi Solanki