Thanks to Karen and Mike for the responses.
The code stops on record 1083.
There is approx. 400 lines of code that executes properly before the process
stops. I have bee unable to determine the exact code line that it stops on as
TRACE or running it outside the timer does not exhibit the problem. The code
does stop inside a structure of:
Declare C1
While
Delare C2
While
While
While
Stopping inside the last while loop.
I have checked for improper breaks, goto's, etc. (It runs fine outside the
timer. )
This is a MRP program running for 1000+ items with multiple nested component
levels for 14 inventory locations. It is a significant chunk of code logic.
It takes about an hour to run, which makes multiple test runs somewhat time
consuming.
I will try the run select suggestion tonight.
Thanks again.
Bob Thompson
LaPorte, IN
219-363-7441
Sent from my iPod
On Aug 22, 2015, at 9:38 AM, "MikeB" <[email protected]> wrote:
> I would be interested to know what the series number of that record was
> compared to Bob's. If they were anywhere near the same, well coincidence I
> do not believe in... ;-)
>
>
>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]] On Behalf Of Karen
>> Tellef
>> Sent: Saturday, August 22, 2015 8:44 AM
>> To: [email protected]
>> Subject: [RBASE-L] - Re: Button EEP versus Timer EEP
>>
>> I sorta suggested the same thing to Bob, but did it privately since he
>> can't see my emails. He has already proved that the timer is part of
>> the issue since he has a button he can press that calls the same CFA
>> and it doesn't fail.
>>
>> I suggested that he take the CFA code and put it in a table and do a
>> "run select" -- like what you're saying with an .rmd. That would be a
>> rather simple thing to try. I also suggested he replace a while loop
>> with goto/label. It's a pain, I know, but it worked for me when I
>> converted a DOS program that looped thru thousands of records and
>> always broke at a certain record#, regardless of what that record
>> happened to be at the time (I would change the "order by" so a
>> different record would come up, but it always quit at a certain
>> record#)
>>
>> Karen
>>
>>
>>
>>
>> -----Original Message-----
>> From: MikeB <[email protected]>
>> To: karentellef <[email protected]>
>> Sent: Fri, Aug 21, 2015 9:33 pm
>> Subject: [RBASE-L] - RE: Button EEP versus Timer EEP
>>
>>
>> I'm going to suggest a couple of brute force methods, just to rule
>> out...
>>
>> Well let's take the timer clear out of the picture, just to rule out
>> coincidence, that the timer is somehow misbehaving.
>>
>> Put the DC_MRP
>> code in a table (You know, VarChar data and a RUN SELECT) or just in an
>> RMD file.
>>
>> When the timer fires, close the form, when the DC_MRP completes, re-
>> launch the form.
>> That will still mechanize the process, but take the timer out of the
>> loop.
>>
>> You might also put everything in just a variable form (If you are
>> disconnecting the db, a variable form will still work) just to see if
>> it relates just to an External Form.
>>
>>
>>
>>
>>
>>
>>> -----Original
>> Message-----
>>> From: [email protected] [mailto:[email protected]
>>> <mailto:[email protected]?> ] On Behalf Of
>> Bob
>>> Thompson
>>> Sent: Friday, August 21, 2015 8:04 PM
>>> To:
>> [email protected]
>>> Subject: [RBASE-L] - RE: Button EEP versus Timer EEP
>>
>>> I have been away from the office all day, thus the delay in
>> responding.
>>
>>> Yes, the first command line is to turn off the timer.
>>>
>>> It runs once
>> per night.
>>>
>>> I have tried different times to insure no conflicts with
>> backup
>>> routines etc.
>>> The oddity is that it stops on the same place each
>> time. Again only
>>> when called from the timer.
>>>
>>>
>>>
>>> Bob Thompson
>> LaPorte, IN
>>> 219-363-7441
>>>
>>> Sent from my iPod
>>>
>>> On Aug 21, 2015, at
>> 4:53 PM, "MikeB" <[email protected]> wrote:
>>>
>>>> I was looking for
>> coincidence..
>>>>
>>>>> -----Original Message-----
>>>>> From:
>> [email protected] [mailto:[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]?>
>>>>>> <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
>
>
