Restricted built-in and timers
From: N. Rangaprabhu <ranga_at_mobinfo.com>
Date: Thu, 24 Jun 1999 09:38:50 -0700
Message-ID: <37725F1A.EA801000_at_mobinfo.com>
Hi,
[Quoted] [Quoted] We have a master-detail form. When we change certain fields in the master block, we need to then show changes on certain fields of the detail block. This means calling a restricted built-in (go_block) from a post-text-item or similar trigger. This is impossible to do, hence we use a timer as follows:
In the post-text-item trigger we create the timer with a period of 1 and no repeat. Then at form level when-tigger-expired trigger we perform the go_block and the required changes to the detail block. Unfortunately this only works 50% of the time. Oracle acknowledges that their timer mechanism is unstable, but are unable to offer any reasonable alternatives. Has anyone faced this problem and how have you dealt with it? We would really appreciate an alternative workable solution as we are in a desperate situation.
Date: Thu, 24 Jun 1999 09:38:50 -0700
Message-ID: <37725F1A.EA801000_at_mobinfo.com>
Hi,
[Quoted] [Quoted] We have a master-detail form. When we change certain fields in the master block, we need to then show changes on certain fields of the detail block. This means calling a restricted built-in (go_block) from a post-text-item or similar trigger. This is impossible to do, hence we use a timer as follows:
In the post-text-item trigger we create the timer with a period of 1 and no repeat. Then at form level when-tigger-expired trigger we perform the go_block and the required changes to the detail block. Unfortunately this only works 50% of the time. Oracle acknowledges that their timer mechanism is unstable, but are unable to offer any reasonable alternatives. Has anyone faced this problem and how have you dealt with it? We would really appreciate an alternative workable solution as we are in a desperate situation.
Thanks for your IMMEDIATE RESPONSE, Ranga Received on Thu Jun 24 1999 - 18:38:50 CEST