Re: Restricted built-in and timers

Hello,

we have had the same problem.

We now set a :GLOBAL.last_validate_item (or a form PARAMETER ) variable in the WHEN-VALIDATE-ITEM Trigger of fields with special actions. In the trigger WHEN-NEW-ITEM-INSTANCE you have the possibility to do restricted built-in functions.

We have made a WHEN-NEW-ITEM-INSTANCE trigger on form level which checks the last_validate_item and makes some action. Then set last_validate_action to NULL. You still will have problems, if you make changes in a field and then press for example save without moving to the next field. There you have to do also a workaround....

Markus

N. Rangaprabhu <ranga_at_mobinfo.com> schrieb in im Newsbeitrag: 37725F1A.EA801000_at_mobinfo.com...
> Hi,
> 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 Fri Jun 25 1999 - 08:28:00 CEST