Hi dears,
can any body tell me , how to use New & Old qualifier which we use at database level Triggers on Insert , delete or Update.
Any clue & idea which help me to track Old and new Field's value which i 've to use in History File.
waiting response...............
Regards,
Ahmad

As far as I can tell, you can't do that; Forms don't know ":old" and ":new" (by the way, as you obviously know how to use them in a database trigger, why don't you do it that way - in the database level (instead of application one))?

You'll have to do it manually: store "old" item value into a parameter (or a global variable) and manipulate with this value (as well as a new one) in one of Forms triggers (PRE-COMMIT, for example).

Yes dear you are right i should use database trigger.
here is my situation:-
I want to know which Applicaton user change the salary Field. so how i can track Application User Information in that way.I am using Oracle DS 10g.I can track the DB user inforamtion in that way.
Hope u understand my problem .
Thanks in Advance.
Regards,
Ahmad

Actually the situation here is that we are using a table in which all user informaiton is reside.when user logon to the application , User authenticate from that table mean his username & password.Now after Logon to the appliation , i just want to track which application User change the field to mantain the history Of any table.when user change a field value , how i will keep track old value & new value Of that field to maintain the history.????
that is my question .
I cant pass any parameter to database trigger
hope so u better understand the scenrio now.
warm Regards,

Do you use the 'osuser' to access this table of user information? What DO you use to identify a user in this table?

To get this to work at the database level pass some identifier of the user who made the changes (irrespective of whether it is the field in which you are interested) in a field of the record. Then, in the trigger, see if the NEW and OLD version of the field in which you are interested is different. You would not appear to need to worry about the other fields. If it is different then either use the information passed in the 'user' field of the table or possibly the 'osuser' if the 'user table' is keyed on that information. Remember, the user/invoker of the trigger is YOU, not Oracle. It is YOUR transaction. You can test this by using a test trigger on a test table.

Now i want to use "User_id" reference in History table to track DML operation on trasactional Tables.
OSUSEr is also helpful and use in my history table as well but i specifically require User_id reference in that history table.
Warm Regards ,
Ahmad

Then add a 'mod_by_user_id' to the table in which you are interested and in your database trigger, if the field of interest has been changed, use the 'mod_by_user_id' field to populate your history file.