On Fri, 26 Mar 2004 04:36:57 +0000 (UTC), sllimr7139 wrote:

>>
>> Is there anything in particular that we (as IBO developers/users) should
>> look out for?
>
> As one of the test case providers of the bug in question, I have to
> say that there are a number of symptoms to this particular bug which
> has made it hard to track down, as I understand it. I spent about 10
> hours trying to eventually confirm that it ended in an API call in the
> client dll, everything upto that point always looked good as far as I
> could tell.
> ...
> The (short-term?) solution that Nickolay presented us was to run with
> the IB_Connection.CacheStatementHandles set to false. This appears
> to fix the bug for the time being but it's hard to tell yet what kind
> of performance impact that may or may not have on our connections.

Thanks for the explanation.

What about any consequences of setting IB_Connection.CacheStatementHandles
to false.
Severe/.../insignificant impact on response times, or what?


Regards,
Aage J.