Re: Forms 4.5 commit

Hi,

My experience is that when you don't commit no changes are committed, but when you do you get this message. That's because Forms detects that there are no database-changes in the FORM, but the database changes made by the procedure are committed anyway! I simply solved this problem by setting the message-level to a value that suppresses the message, and after the commit back to the lowest level:

COPY ( '5', 'SYSTEM.MESSAGE_LEVEL');
COMMIT_FORM;
COPY ( '0', 'SYSTEM.MESSAGE_LEVEL'); I admit, it's kinda ugly too, but it should do the trick.

H. Hultink
Software Engineer
Stoas, Division IOAL
Wageningen, The Netherlands
"Activating Knowledge"
http://www.stoas.nl

e-mail: hhu_at_stopspam.stoas.nl (you know what to do...)

[Quoted] "Mark Styles" <news_at_lambic.co.uk> wrote in message news:bl2lvtklte5snar4uamokcthcbs47pu1hv_at_4ax.com...
>
> I have an Oracle 4.5 form, which calls various stored procedures.
> Those procedures make database changes.
>
> My problem is Oracle Forms doesn't recognise that the procedures have
> made changes, so when I issue a commit (which gets auto-magically
> converted to a 'COMMIT_FORM'), I get the message 'no changes to be
> applied'.
>
> How can I force forms to do a commit? I could call a stored procedure
> which does a commit, but that's kinda ugly. Or I could force the form
> into a Changed state, but that's not very pretty either.
>
> Thanks.
>
Received on Fri Nov 23 2001 - 13:27:15 CET