Re: EXCEPTION handling

Hi Richard,

if You use an ON-ERROR and an ON-MESSAGE-trigger on Item-, Block- or Form-Level You can use the variables ERROR_TYPE, ERROR_CODE and ERROR_TEXT or MESSAGE_TYPE, MESSAGE_CODE and MESSAGE_TEXT to examine the error an then decide how to handle it. In the Online-Help of Forms-Builder are also examples under the topics ON-ERROR Trigger and ON-MESSAGE Trigger.

I hope this will be helpful for You
Christoph Ernst
GRASS GmbH - Langenlonsheim
http://www.grass-gmbh.de

In article <36748B7D.A0175DC7_at_cmc.net>,
  rdowdy <rdowdy_at_cmc.net> wrote:
> I am using Oracle Forms 5, and need to create some exception handles for
> a specific button trigger. Is there a simple method to ensure all
> exceptions are handled?
>
> I have a form where I affect multiple tables that depend on one another,
> so it seems necessary to 'commit' after changes. On certain occassions,
> these commit(s) bring a few errors to either the status line or a popup
> window with errors such as:
> No changes to save, FRM-40475, ORC-10001
>
> I'm pretty certain proper programming technique could eliminate these
> errors. I tried using a conditional commit statement (~IF form changed
> THEN commit END IF), but this caused some problems.
>
> Thank you for your time.
> Richard W. Dowdy
> -Client Development Leader-
> -SAP/Oracle/Unix help desk project-
> - richdow_at_thegrid.net -
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Tue Dec 15 1998 - 00:00:00 CST