Re: Getting 'No changes to Save' After Commit in Forms?

The COMMIT is operating in the form as well as in the database. Because you have not changed the current record in the form, there are no *form* changes to save. The *insert* is committed, however.

The error message is a low-level error that can be easily suppressed. Instead of a simple commit, do this:
:system.message_level := 5;
 commit;
:system.message_level := 0;

Purists would have you retrieve and save the current message-level, increase it by 5, and then restore it after the commit.

"Amanda Zaborowski" <azaborow_at_mindspring.com> wrote in message news:8o3dml$rf6$1_at_slb6.atl.mindspring.net...
> I have developed a form to insert info into a table...it is inserting the
> data into the table just fine (when I do a select in SQLPlus, all data is
> there), with a procedure that selects from a table, then inserts this
 data,
> along with data that the user has entered, into another table.
> Unfortunately, it seems, after the commit in the procedure, Oracle tries
 to
> do another save, and I end up getting the error 'FRM-40401 - No changes to
> save.' Also, if I include an error checking statement in the form
> (:ERR_MSG_DISPLAY := SQLCODE), it not only gives me the error above, but
> then goes further, and gives the generic message 'Unable to INSERT'....
>
> I hope this is clear, and that someone could tell me how to get rid of
> whatever Oracle is doing in the background to cause these messages. I had
> asked an instructor about this previously, in a Developer class, and his
> answer was 'Don't worry about that message.' If I had only known the
> problems this would cause!!!
>
> Thanks so much in advance - I am at my wits end!
>
> Amanda
>
>
Received on Mon Aug 28 2000 - 17:19:35 CEST