Re: Restricted built-in and timers

A technique we used in forms3 (no timers existed) was making a dummy field (invisible)
after the field that could be changed. This dummy field comes in sequence right after the other field. On that dummy field a WHEN-NEW-ITEM-INSTANCE fired in wich we could do the restricted procedures. This method still works for later forms versions.

It's a bit trick tricki and rather dirty way of programming but it works. If you do this DOCUMENT it, otherwise no-one can get wat you ment to do.

N. Rangaprabhu <ranga_at_mobinfo.com> schreef in berichtnieuws 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 Wed Jun 30 1999 - 23:20:06 CEST