Carlos, do you need us to write a .NET application that exhibits this behavior and is small enough to distribute in some way? We've only seen this within our app, which of course we cannot send around, so we'd need to write something new. Or is there any other information we could provide you with, say the section of our code in which we interact with the database, or answers to any questions on our usage of the .NET provider, or something we could try on our end to see if that solves the problem?
Thanks,
Uri
On 11/30/05, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote:
Hello:
> The underlying ISC error is "invalid statement handle". These may be
> due to .NET garbage collection, or to the .NET Firebird DataProvider
> we use, or to Firebird itself -- we just don't know enough to tell.
> We've *never* seen these before we turned Pooling off. Plus, with the
> embedded server, we thought there would be only one connection anyway
> (and yes, we're single-threaded when accessing the database). Any
> suggestions as to why this might be happening, or where we should go
> ask this question, or why we shouldn't use Pooling=off to begin with?
>
CAn you send a test case please ??
--
Carlos Guzmán Álvarez
Vigo-Spain
carlosga.blogspot.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
