Re: ASK FOR COMMIT BEFORE LEAVING A RECORD INSTANCE.
From: (wrong string) égis <olivier.regis_at_duroblade.com>
Date: Mon, 27 Sep 1999 14:34:36 +0200
Message-ID: <7snnup$gaa$1_at_news.worldcom.ch>
Date: Mon, 27 Sep 1999 14:34:36 +0200
Message-ID: <7snnup$gaa$1_at_news.worldcom.ch>
YANN,
MY PROBLEM IS THAT I MUST COMMIT IN THE ANSWER IS YES.
HERE'S IS MY CURRENT POST-RECORD TRIGGER AT FORM LEVEL:
COMMIT DOESN'T WORK IN THIS TRIGGER...
[Quoted] I WANT A COMMIT SUCCESSFULL EVERYTIME THE USER PRESS "YES" AND EVERYTIME
THERE'S CHANGE IN A RECORD.. AND WHEN NAVIGATING TO ANOTHER RECORD OF EVERY
BLOCKS..
HAVE YOU A SOLUTION TO RESOLVE THE "COMMIT".. ??
THANKS
OLIVIER
declare
answer number;
begin
if :system.form_status != 'QUERY' then
if :system.record_status in ('CHANGED','INSERT')
then
SET_ALERT_PROPERTY ('ALERT_YES_NO',ALERT_MESSAGE_TEXT,'COMMIT CHANGES ?');
answer := show_alert('Alert_yes_no');
if answer = ALERT_BUTTON2 then
raise form_trigger_failure;
end if;
--Enter; -- force the validation to happen first -- if not form_success then -- bell; -- my_show_alert_caution(null,'Validation failed');
- raise form_trigger_failure;
- end if;
commit;
--DO_KEY('COMMIT_FORM');
bell;
--if :system.form_status <> 'QUERY' then
--bell;
--my_show_alert_caution(null,'An error prevented your changes from
being commited.');
--raise form_trigger_failure;
- end if; end if; end if; end;
- end if;
commit;
--DO_KEY('COMMIT_FORM');
bell;
--if :system.form_status <> 'QUERY' then