Re: Forms 4.5 bug OR My program's bug

From: Steve Cosner <stevec_at_zimmer.csufresno.edu>
Date: 1997/12/24
Message-ID: <882981923.1777926147_at_dejanews.com>#1/1


In article <882943626.994508802_at_dejanews.com>,   rajs_at_meghdoot.mastek.com wrote:
>
> Hi Everybody,
> Have I found a new bug in Forms 4.5 or does my application have a bug?
>
> 1) My Form module is referencing a Master Form module which contains
> a generic code for KEY-DELREC and PRE-INSERT (at Block Level) and used
> through out our application by referencing it.
>
> But my present Forms module has the requirement which has forced me
> to create a (local) KEY-DELREC and PRE-INSERT at form level.
> I have changed the setting of Override Trigger Execution which
> fires my local KEY-DELREC/PRE-INSERT and not the referenced ones.
>
> I raise the FORM_TRIGGER_FAILURE exception in my local
> KEY-DELREC/PRE-INSERT triggers. I expect that the the record does not
> get deleted. But lo!! Behold, the referenced KEY-DELREC/PRE-INSERT also
> fire and perform the code and actually delete the record. What am I
> doing wrong and if I am, how do I work around it??? I want my local
> triggers to take over the operation of my referenced triggers for only
> this particular module. I would appreciate an early response. REgards
> Rajs

Block level triggers ALWAYS run regardless of the form-level trigger. So the local one you created at the form level may or may not run depending on what you set the block-level trigger's Execution Style property to. The only way to prevent the block-level trigger from running is to delete it, or create an item-level trigger on each item in the block (with Execution Style set to Override), that does the special processing you need.

Regards,
Steve Cosner



http://members.aol.com/stevec5088 -- downloadable QA utility form: Dynamic display and update access to any table.
-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet
Received on Wed Dec 24 1997 - 00:00:00 CET

Original text of this message