Re: developer 2000 -navigation
Date: 2000/05/29
Message-ID: <8gt532$gen$1_at_nnrp2.deja.com>#1/1
It mustn't work because help says:
"A When-Timer-Expired trigger cannot fire during
transactions, trigger processing, navigation, etc.
Thus, a When-Timer-Expired trigger only fires
while Form Builder is waiting to accept user
input.
As a result, a timer may not expire
exactly on the millisecond, but it will fire after
the specified number of milliseconds."
If user presses Key-Commit, for example, Forms
will perform commit before When-Timer-Expired
trigger will fire.
In article
<zoeX4.57$XQ1.15547_at_wdc-read-01.qwest.net>,
"Mike Dwyer" <dwyermj_at_co.larImer.co.us> wrote:
> Others have suggested creating a timer in
post-record, putting the go_block
> in a when-timer-expired trigger.
>
> I haven't tried it myself, but maybe it will
work.
>
> "Mike Kogan" <kogan_at_mtt.cell.ru> wrote in
message
> news:392D1ED8.72B554C7_at_mtt.cell.ru...
> > Hi everyone!
> >
> > It's necessary when a user goes out from a
record by any manner he gets
> > to a record of another block immediately .
Exit triggers like
> > Post-Record or When-Validate-Record are
restricted therefore I can't use
> > Go_Block built-in at them. Using of Go_Block
built-in in 'arriving'
> > triggers (like When-New-Record-Instance) and
in all user's actions
> > resulting in an exit from a record is a bad
way because it's difficult
> > to do.
> >
> > Thank you very much for your help and kind
attention.
> >
> > --
> > Best regards,
> > Mike Kogan
> >
> > PS: I use Forms 5. Does Form 6 resolve the
above problem?
> >
> >
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Mon May 29 2000 - 00:00:00 CEST