Yes Phil,

Strange that neither is the case with our app and a host of people are
getting this error. It also strange that it can be reproduced in a
smallish app.

And I must be strange too because I would welcome it to be my fault,
then I could have fixed it 18 months ago. Instead I have been trying to
convince others and relying on them to do something about it.

Just maybe you dont have a problem because you have a rather simplish
application. :-)

Phil Shrimpton wrote:

>On Saturday 28 February 2004 11:20, Rohit Gupta wrote:
>
>Hi,
>
>
>
>>We have been plagued with it too. Unfortunately, our clients are ready
>>to throw the app out and our reputation is mud. We have not convinced
>>anyone that its not our coding.
>>
>>
>
>Well, it probably is your coding <g> I have used FB (and IB) for years, and
>the only time I have had these errors are when I
>
>- Use 2 or more connections with the Local protocol
>- Access the same connection via two or more threads
>
>It is fairly easy to recreate the errors posted in this thread with either of
>those conditions.
>
>Phil
>
>