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
The problem is that your procedure does a commit. When it is Forms turn to
commit, there is nothing left to commit.
The solution...
One is to remove the COMMIT from your insert operation (is it on the on-insert
trigger?). When the on-insert code is finished, a commit will be performed as
part of the process.
Another possibility is to put some code in the on-commit trigger. Then, when
forms would do a commit, it would do the code in the on-commit trigger, which
is nothing, and go on. [I haven't tried this method though]
Dan Hekimian-Williams
In PL/SQL, Forms translates COMMITs to COMMIT_FORM
procedure, as well ROLLBACKs to CLEAR_FORM procedure.
If you want to do a *database* commit or rollback,
you can use the package DBMS_TRANSACTION:
dbms_transaction.commit;
dbms_transcation.rollback;
Of course, these do not commit or rollback data
in the form itself.
In article <8o3dml$rf6$1...@slb6.atl.mindspring.net>,
Sent via Deja.com http://www.deja.com/
Before you buy.
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" <azab...@mindspring.com> wrote in message
news:8o3dml$rf6$1...@slb6.atl.mindspring.net...