Re: [Firebird-net-provider] Faulty GdsConnection::NextOperation

2007-12-14 Thread Frode Nilsen
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sent: Friday, December 14, 2007 12:24 PM To: For users and developers of the Firebird .NET providers Subject: Re: [Firebird-net-provider] Faulty GdsConnection::NextOperation Hello: Nah, not a complete one. The fault

Re: [Firebird-net-provider] Faulty GdsConnection::NextOperation

2007-12-14 Thread Carlos
Hello: Nah, not a complete one. The fault is a bit random, and you need a lengthy > dataset to stumble across it (I can't post you our customer database :). > without a test case it's going to be hard difficult to solve the problem, what si the character set of the database and the one you are u

Re: [Firebird-net-provider] Faulty GdsConnection::NextOperation

2007-12-14 Thread Frode Nilsen
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sent: Friday, December 14, 2007 9:00 AM To: For users and developers of the Firebird .NET providers Subject: Re: [Firebird-net-provider] Faulty GdsConnection::NextOperation Hello: The "spinner" in GdsConnection::Next

Re: [Firebird-net-provider] Easy way to know the idkey of a registry just inserted?

2007-12-14 Thread Mercea Paul
Hi Why don't you use a stored procedure for this? For FB2.X in doc section in README.returning.txt you can find this: INSERT INTO T2 (F1, F2) VALUES (1, 2) RETURNING ID INTO :PK; This return desired value, that you can insert in second table! Regard's Paul > -Original Message-