On Nov 26, 2003, at 10:48 AM, Aparajita Fishman wrote:
I believe that both Active4D and my report are off the hook for now, but I don't believe the issue has been resolved yet. Either way, I'll keep you posted.
I would be very grateful if you could duplicate the code purely within 4D and hopefully duplicate the behavior. This would completely eliminate Active4D as a factor, then you could proceed to go the iNUG and 4D and see if it is a (known) 4D bug.
Further follow-up:
After hitting the Monkey, I found a lot of complains of 4D Internet Commands not yielding to the scheduler. Sure enough, we put some code in a trigger a few weeks ago that sends a few tidbits over the network with 4DIC when records in one of our tables is changed, to keep another one of our internal applications up-to-date. We were able to reproduce a large part of the problem by exercising this code under suboptimal conditions, and are now pursuing that avenue.
- Dave
--
David P Kleinschmidt Software Development Bristol Capital, Inc. 160 Summit Ave Montvale, NJ 07645 Tel: 201.476.0600 x204 Fax: 201.476.9440 [EMAIL PROTECTED]
