Re: Restricted built-in and timers

yes it will work, but it won't if you want to change several detail records....

Markus

Jerry Alan Braga <jabraga_at_golden.net> schrieb in im Newsbeitrag: 7l0ilb$an0$1_at_cougar.golden.net...
> you can reference the values in the other datablock directly
> by using :detail_block.item1 : = 'Some value';
>
> this should refresh automatically
>
> if it does not, issue a synchronize command after the assignments.
>
> This is assuming that you do not have to navigate into the block due to
> those conditions
>
>
>
>
>
> N. Rangaprabhu wrote in message <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 Mon Jun 28 1999 - 08:20:36 CEST