Re: How to grab the name of a failing trigger in Form4.5

Hi Steve,

I agree it is not neccessary to use exception-handling part in simple (errors free) triggers. But when I use exception clause in comlicated PL/SQL units I use it even in all anonymous blocks even in one trigger or procedure body because I want to catch every error with its place precisely.

I agree that many Forms Developers aren't sure about using EXCEPTION clause and FORM_SUCCESS built-in function (they must use form_success to trap the success or failure of a built-in subprogram, for example), but if we sure about that we must tell them :)

By the way, you are right. If you can catch error without exception clause, and you are sure this error will not appear to end-user, it is better to avoid the complicated coding.

Good Luck.
Valeri

stevec_at_zimmer.csufresno.edu wrote:
>
> I agree that Loyal Barber's example would be more difficult to trap. But that
> is more an unusual situation, and not the normal one.
>
> I will stick by my original recommendation to run the form with
> debug_messages=on, and see what pops up. The original poster said it was an
> On-Error trigger that was running. So all he needs to do is keep track of
> each trigger that started, and as soon as On-Error shows up, then it was the
> one immediately before that one. If not that one, then look into the one
> just prior, etc. It would not be a long trail to trace before he found the
> problem.
>
> Writing an exception handler in EVERY trigger just because you have a single
> one failing in your form is a bit too much work for me. Besides, most Forms
> developers aren't even sure when when to code EXCEPTION WHEN... and when to
> code IF NOT FORM_SUCCESS THEN...
>
> I write exception handlers ONLY when absolutely necessary, and I believe the
> code is much easier to maintain.
>
> Steve Cosner
>
> In article ?371ED179.B4A78CCD_at_dd.ru?,
> Valeri Sorokine ?vsorokin_at_dd.ru? wrote:
> ? As far as I know the better way is using exception–handling part in each
> ? PL/SQL unit :), as mentioned by Patrick Flahan.
> ?
> ? Loyal Barber wrote:
> ? ? Steve Cosner wrote:
> ? ?snip?
> ? ? ? Run the form with debug messages turned on.
> ? ?snip?
> ? ?
> ? ? This might be a bit misleading.
> ? ?
> ? ? If I have trigger A which raises trigger B then trigger
> ? ? A resumes at the conclusion of B, I will see a display indicating
> ? ? that A fired then B then I will get my error.
> ? ?
> ? ? So in this case, even though the error occurred in A, I would think
> ? ? it occurred in B.
> ? ?
> ? ?snip?
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

--
Valeri Sorokine
ProSoft, Russia, Moscow, Information Systems Division Phone: +7 (095) 234 0636 (6 lines) FAX: +7 (095) 234 0640 E-mail: vsorokin_at_dd.ru OR vsorokin_at_prosoft.ru http://www.dd.ru Received on Mon Apr 26 1999 - 03:41:30 CDT