Re: FRM-40401 No Changes to Save (Forms 4.5)

Dave:

This is actually expected and documented behavior and is not a bug. Any ancillary DML statement that you issue is not part of the transaction from a Forms perspective (i.e. the forms sees nothing has changed) However, it is still part of a session's transaction and may be committed when a subsequent change to a base-table block and commit is issued.

You must issue a delete_record on a row in a base-table block in the form in order to have the form in sync with your transaction. If you don't, the deleted record may be rolled back (as part of the session's transaction) when the user
exits the form having made no other changes.

Hope this helps.

-dave fischer / DBA
burlington coat factory
davidf_at_coat.com

> From owner-oracle-l_at_CCVM.SUNYSB.EDU Fri Jan 12 03:50:24 1996
> Reply-To: "ORACLE database mailing list." <ORACLE-L_at_ccvm.sunysb.edu>
> Sender: "ORACLE database mailing list." <ORACLE-L_at_ccvm.sunysb.edu>
> Subject: FRM-40401 No Changes to Save (Forms 4.5)
> X-To: oracle-l_at_ccvm.sunysb.edu
> To: Multiple recipients of list ORACLE-L <ORACLE-L_at_ccvm.sunysb.edu>
> Content-Length: 534
> X-Lines: 17
>
> This is strange...
>
> On a form, I have a delete button that deletes the displayed record from the
> database:
>
> delete x where pn=:block.var; (I've attempted 'delete_record' also)
> commit;
>
> The commit does its job and removes the record from the database, but, I get
> the error FRM-40401 No Changes to Save when the commit executes. There is no
> second commit happening. (I take the commit out and there is no error, the
> delete is not committed). 'pn' is a primary key on the table.
>
> Any help would be appreciated.
>
> TIA
> Dave
>
Received on Fri Jan 12 1996 - 09:57:30 CST