Re: [Firebird-net-provider] 10054 errors in firebird log file

2010-01-18 Thread russ3ell
I have tried creating a solution and project, but I am having difficulties. The build seems to require DbProviderFactory which is not available for Compact Framework. I really would like a build for Compact Framework v2.0 -- View this message in context: http://old.nabble.com/10054-errors-in-f

Re: [Firebird-net-provider] 10054 errors in firebird log file

2010-01-15 Thread russ3ell
I have tried downloading NETProvider_2.5.1 and built it using the solution. However, when I compile my application I get the following error: Error 1 The type 'System.Data.Common.DbConnection' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.

Re: [Firebird-net-provider] 10054 errors in firebird log file

2010-01-15 Thread russ3ell
That would be great thanks -- View this message in context: http://old.nabble.com/10054-errors-in-firebird-log-file-tp27169214p27179201.html Sent from the firebird-net-provider mailing list archive at Nabble.com. -- T

[Firebird-net-provider] 10054 errors in firebird log file

2010-01-15 Thread Russell Rose
>From VS2008, I get the runtime Version as 2.0.50727 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to le

Re: [Firebird-net-provider] 10054 errors in firebird log file

2010-01-14 Thread Jakub Czyżkowski
Hi, you schould use last version of FirebirdClient (2.5.1), which is available on Sourfoge. I've just compiled this for myself, becouse compiled .dll is targeted .NET 3.5, but I needed for .NET 2.0 If you whant I could send you .csproj file for build CF FirebirdClient under VS2008 and .NET

[Firebird-net-provider] 10054 errors in firebird log file

2010-01-14 Thread Russell Rose
I am getting lots of 10054 errors in my log file. These occurs during the fetch cycle of a read. I have tried changing the fetch size, but it doesn't make any difference. I have looked on the net and in some previous occasions it was because of the client that was being used. I am using serv