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 [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
