Hi,

At November 10, 2005, 6:13 PM, Ulf Grasse wrote:

> I think a good resolution would be to add a property to disable this
> well-intentioned optimization either on database level or statement
> level (or even both). While this is probably a good optimization for
> the majority of applications out there, in our case it seems to
> impact performance rather negatively.

Did you try setting the TIB_Connection.CacheStatementHandles property
to False?

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)