Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Martin Turek
Hi! I've got a problem with the new version, and I don't know what it is. Maybe it's not a problem with the version. I've created a command: String sqlStreams = INSERT INTO STATIONDETAILS_STREAMS (STATIONDETAILSID, URL, FORMAT, BITRATE, PLAYLIST) VALUES (@param1, @param2, @param3, @param4,

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Jiri Cincura
On Fri, Nov 19, 2010 at 09:15, Martin Turek tur...@bury.com wrote: Can you help? You're trying to insert longer field than it's in database. Either provide proper value or specify size of param explicitly (and let DB handle it). And why the hell I get your path on my computer in the

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Martin Turek
Hi! Yes, there ist he pdb file. I've changed the code to ... cmdSts.Parameters.Add(param5, FbDbType.VarChar, 5); ... But it's still the same problem. The field I in the database is varchar(10) and the value is only true or false (as I wrote). They CAN'T get longer than 5. So, where the

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Jiri Cincura
On Fri, Nov 19, 2010 at 10:07, Martin Turek tur...@bury.com wrote: But it's still the same problem. The field I in the database is varchar(10) and the value is only true or false (as I wrote). They CAN'T get longer than 5. So, where the problem? Who said, it's param5? What about param2 or

[Firebird-net-provider] R: ADO.NET provider 2.6.0 for Firebirdreleased

2010-11-19 Thread Luigi Piccinni
Could the problem be on param2 or param3? Try to limit them, too. Luigi. -Messaggio originale- Da: Martin Turek [mailto:tur...@bury.com] Inviato: venerdì 19 novembre 2010 10.08 A: firebird-net-provider Oggetto: Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Martin Turek
Well, when I comment out param5 it runs without problems! Martin -Ursprüngliche Nachricht- Von: Jiri Cincura [mailto:disk...@cincura.net] Gesendet: Freitag, 19. November 2010 10:16 An: For users and developers of the Firebird .NET providers Betreff: Re: [Firebird-net-provider] ADO.NET

[Firebird-net-provider] R: ADO.NET provider 2.6.0 for Firebirdreleased

2010-11-19 Thread Luigi Piccinni
Ops, sorry.. I didn't see this answer :) Luigi -Messaggio originale- Da: Jiri Cincura [mailto:disk...@cincura.net] Inviato: venerdì 19 novembre 2010 10.16 A: For users and developers of the Firebird .NET providers Oggetto: Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Jiri Cincura
On Fri, Nov 19, 2010 at 10:44, Martin Turek tur...@bury.com wrote: Well, when I comment out param5 it runs without problems! Looks like somewhere the parameter size or the value itself is longer. The check there is: string svalue = param.DbValue.GetString(); if ((param.Length %

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Martin Turek
Sorry, guys, you're right! I've limited the other params and it's ok! Thanks! Regards Martin -Ursprüngliche Nachricht- Von: Jiri Cincura [mailto:disk...@cincura.net] Gesendet: Freitag, 19. November 2010 11:03 An: For users and developers of the Firebird .NET providers Betreff: Re:

Re: [Firebird-net-provider] ADO.NET provider 2.6.0 for Firebird released

2010-11-19 Thread Jiri Cincura
On Fri, Nov 19, 2010 at 12:24, Martin Turek tur...@bury.com wrote: Sorry, guys, you're right! I've limited the other params and it's ok! No problem. Sometimes I'm debugging wrong code too. :D -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com

Re: [Firebird-net-provider] using Windows authentication

2010-11-19 Thread Jiri Cincura
On Fri, Nov 12, 2010 at 16:17, Rick Roen r...@lakevalleyseed.com wrote: and I get AccessViolationException with Attempt to read or write protected memory… If I do not set the UserId and Password at all, I get an InitializeSecurityContext failed message. I have a feeling it's 64bit related.