I was looking for coincidence..
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Karen
> Tellef
> Sent: Friday, August 21, 2015 11:44 AM
> To: [email protected]
> Subject: [RBASE-L] - RE: Button EEP versus Timer EEP
>
> Mike: he mentions that he turns the timer off as it calls the CFA.
> I've done this before, and you turn it back on when it's done.
>
> Karen
>
>
>
>
> -----Original Message-----
> From: MikeB <[email protected]>
> To: karentellef <[email protected]>
> Sent: Fri, Aug 21, 2015 10:35 am
> Subject: [RBASE-L] - RE: Button EEP versus Timer EEP
>
>
> What is the frequency of the timer poll? Does the crap-out occur at
> that instance? Do you have a flag (file or variable) that can be set
> when the timer fires so that if it fires again it won't call the custom
> form action?
>
>
>
> >
> -----Original Message-----
> > From: [email protected] [mailto:[email protected]
> > <mailto:[email protected]?> ]
> On Behalf Of
> > [email protected]
> > Sent: Friday, August 21, 2015 9:35 AM
> >
> To: [email protected]
> > Subject: [RBASE-L] - Button EEP versus Timer EEP
> >
>
> > I have an issue that I have been unable to discover the cause and
> > would
> >
> appreciate any thoughts.
> >
> > (Ver. 9.5 64)
> > Compiled application.
> >
> > I
> have an external form that has a custom form action named DC_MRP
> >
> > This
> external form has a timer on it that checks the time of day and at
> > a set time
> calls the custom form action.
> >
> > I also have a an office button on the same
> form that calls the custom
> > form action if I choose to run it "manually"
> versus automatically from
> > the timer.
> >
> > Now for the issue.
> >
> > When
> the timer calls DC_MRP, it starts and runs partially through the
> > eep and then
> stops. It does not crash, the program simply stops and
> > returns to the
> form.
> >
> > There is a progress message that shows the record number being
> >
> processed and it always stops on the same record.
> >
> > If I push the office
> button which calls the DC_MRP action, it runs
> > completely through every time
> without issue.
> >
> > The calling code is exactly the same other than one is in
> the timer and
> > one is in an office button. (The code disables the timer
> before
> > calling the DC_MRP action)
> > The only difference is the calling code
> resides in an IF statement. I
> > have triple
> > checked that there is no issue
> with the syntax. I have RStyled the eep
> > and there
> > is no open IF or While
> statements. I even placed an IF statement in
> > the office
> > button and it
> runs ok.
> >
> > If I trace, it always runs without issue. I have checked the
> one
> > record and there is
> > nothing incorrect with the data. Running it via
> the office button,
> > runs fine anyway, so it is not a data issue.
> >
> > If the
> program stops after being initiated by the timer, I can click
> > the office
> button immediately
> > afterwards and it will run completely through without
> issue.
> >
> > Does anyone know of anything about the timer function that might
> cause
> > an EEP to run
> > differently than from an office button? The DC_MRP
> action is a
> > rather complex program
> > that takes about 45 minutes to run.
> However I do turn off the timer
> > at the beginning of the code.
> >
> >
> Thanks,
> > Bob
>
>
