You nailed it! The problem was in a trigger.

Thanks very much,
Steve


-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of André Knappstein,
Controlling
Sent: Monday, August 04, 2008 3:39 AM
To: firebird-support@yahoogroups.com
Subject: Re[2]: [firebird-support] Stored Procedure/Transaction Problem

>> 1. Can anyone spot an error in my procedure code that would explain
>> the problem?
>> 2. Is there a limit on the # of inserts within a transaction and

have

>> I exceeded it?
>> 3. Is this a possible bug in the .NET provider?

If there is an error in your procedure, I don't see it; which does not
mean there is none :)
You could return a "result" different from 0 in case of an insert;
right now you are returning -1 if the statement fails in general, and
0 in both cases (insert or update). But that does not explain why
numeric data is going amiss.

Everything has a limit, but 57000 inserts in one transaction isn't one
for Firebird.

I never heard of such a bug, nor did I experience one. I am using .net
provider myself with stored procs.


Question: Do you have _any_ trigger set for that table, and if yes
what is it/are they doing?

ciao,
André