Checking for two database columns is null

Question

hi all,
i am using Forms [32 Bit] Version 6.0.8.24.1 (Production)
i have two questions.
i have database multi record block and fields like code,name,email,p_email,notes
1. if the senario email and p_email both cannot be null
so in when-validate-record i have written like
if email is null and p_email is null then
  raise form_trigger_failure;
end if;what i am doing is correct?
2. if i enter code and name and close the form the form is not asking for commit simply close window is appearing with 'yes' and 'no' option. but if i enter name,code and any of field(email or p_email) then its asking for commit.
my question is why such behaviour is this is because of w-v-r?
but if i update(code and name)alone then the change is reflecting.
Please clarify my doubts.
Thanks..
Edited by: GD on Apr 10, 2011 5:40 AM

Answer 1

hi,
i have written the below code in w-v-r trigger and its firing accordingly
if email is null and p_email is null then
  raise form_trigger_failure;
end if;but in the same i have written the code as below but there is no impact
if email is not null and p_email is not null then
   set_item_property('code',update_allowed,property_false);
else
   set_item_property('code',update_allowed,property_true);
end if;in my second code the trigger is firing after i leave the record, which is of no use(still i can update the code column),
but in my first code form_trigger_failure has been raise if the two colulmns are null(for the same record)
my question is why its behaving in two different manner,according to me the first code should not raise error for the same record as its behaving in second code, otherwise the second code should also fire for the same record(but its firing once i try to move to other record).
Please clarify where i wrong? or is this is how trigger behaves?
Thanks..