> On Oct 25, 2017, at 6:55 AM, Tim Nevels via 4D_Tech <[email protected]>
> wrote:
>
>> Anyway, I'm wondering if the problem is when either Tickcount, Milliseconds
>> or another internal 4D time measure overflows into negative territory. I
>> have no idea internally what measure 4D uses for DELAY PROCESS, nor what
>> data type they use internally for it, but what if they aren't taking account
>> of the overflow when the measure value goes from a large positive number to
>> a large negative.
>>
>> That could explain the large time period before the problem reoccurs??
I am not sure that this is in any way related, but a after upgrading a client
to v15 I started having an occasional problem with a stored procedure. I cannot
remember now exactly what the problem was but I solved it by letting the
process die after starting a new process with the same method and delaying the
new process as soon as it starts…
Process A does it thing starts Process B and dies
Process B is delayed. After delay Process B does it’s thing starts
Process A and dies.
Repeat…
This has worked without any problem since.
John
John Baughman
Kailua, Hawaii
(808) 262-0328
[email protected]
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
