Re: How to change error_level in Forms?
Date: 1996/12/11
Message-ID: <32AF3C79.3BC8_at_mail.stil.scitex.com>#1/1
Ken Denny wrote:
>
> Gary G wrote:
> >
> > There is a know bug in Forms, that throws an error at me, while committing
> > changes to a table: 'No changes to save', ...yea right!
> > I think there is a way to change the level of oracle errors, so that the
> > lower ones are surpassed. Any ideas?
> > Thanks in advance, I would appreciate direct e-mail (for speed)
> > Gary
>
> I assume you're getting this message when your code does a "commit". There
> are two ways I found to get around this. The first way is to set
> :system.message_level to 5 as in:
> :system.message_level:=5;
commit;
> :system.message_level:=0;
>
> This is the way I started out doing it. I always set it back to 0 after the
> commit so as not to miss any other messages which I might want to see.
>
> The second way I found later and like better is to create a stored procedure
> which does nothing but a commit and call that from within forms.
>
> create or replace
> procedure commit_it is
> begin
> commit;
> end;
> /
>
> Now wherever you have a "commit" in your code change it to "commit_it". By
> putting the commit within a stored procedure forms doesn't know about it. I
> have found this trick to be useful for some other things too. For instance, I
> have a procedure called "roll_it_back" which simply does a rollback. The
> reason I do that is because when you do a rollback within a forms trigger it
> clears the screen and I didn't want that to happen.
>
> Good luck
> Ken Denny
> Insight Industries, Inc.
> RTP, NC
> kdenny_at_interpath.com
About "second" way :
instead to create stored procedures you can use
built_in FORMS_DDL.
For example:
forms_ddl('commit');
Slava. Received on Wed Dec 11 1996 - 00:00:00 CET