Re: Form 4.5: Problem with commiting a PL/SQL update statement.

In <4t08vi$9lk_at_natasha.rmii.com>, wdieteri_at_rmi.net (Will Dieterich) writes:
>This has been driving me crazy, so instead of going with my final solution
>of trapping for the error message and then ignoring it I figured I would
>ask here.
>
>This is under the Unix 1.2 version of Developer 2000
>
>I have a canvas that allows users to set and save a varity of default
>setting. The top half of the screen show thier current default setting(this
>is its own block) and does link to any table, and the bottom
>half of the screen allows them to set,
>insert, update, and delete the default setting(this is its own block).
>This way each person can have thier own default settings, and as needed
>the user can select and use the default setting of another person.
>The top half of the canvas is cannot be edited, so the way that a user selects
>which saved setting to use is by a 'Set Default' button. This button sets
>(by use of PL/SQL) the top half fields to the corresponding bottom half values
>then does a SQL update using the values from the bottom half, then a commit
>is done.
>
>The problem I am getting is that whenever I do this is get an
>error message of FRM-40401: No Changes to save. Needless to say if I take
>out the commit, the changes are not saved to the database, but when I leave
>the commit in the changes are saved, but I get the error message.
>I have tried using commit_form, post and a few other Form 4.5 commands that
>perform commits but they all put up thier version of 'No changes to save'.
>
>Does anyone have any other ideas besides just trapping for this error and then
>ignoring it? Thanks.
>
>
>--
>William Dieterich Call Sign: KD4LZE Email: wdieteri_at_rainbow.rmii.com

Have you tried using the forms_ddl built-in to do the commit?

  forms_ddl('commit');

M.Landa Received on Mon Jul 22 1996 - 00:00:00 CEST