Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: ASK FOR COMMIT BEFORE LEAVING A RECORD INSTANCE.
Sorry, I didn't test what I've posted ....
Maybe using WHEN-NEW-RECORD-INSTANCE and a variable to store the position to go back if user choose NO COMMIT:
POST-RECORD trigger:
WHEN-NEW-RECORD-INSTANCE trigger
Does it work better ?
Yann.
"Olivier Régis" a écrit :
> 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...
> 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;
Received on Mon Sep 27 1999 - 08:02:20 CDT
![]() |
![]() |