Concurrency violation with decimal type

  • Thread starter Thread starter hb
  • Start date Start date
H

hb

Situation:

Using a dataset's UpdateCommand, when a decimal type field changes from
integer to decimal, the update goes through. When the field changes from
decimal to integer or another decimal, I get a Concurrency violation: the
UpdateCommand affected 0 records error.

I have used trace to view the CommandText and all the source columns and
parameters. When I try to execute the update statement directly in the
database, the record updates. Just a code issue, apparently. I noticed in a
search of these forums someone else had a similar problem, and they solved
it, but never posted their fix.

Any suggestions? using .NET 1.0 framework w/ ODP.NET data provider.
 
hb said:
Situation:

Using a dataset's UpdateCommand, when a decimal type field changes from
integer to decimal, the update goes through. When the field changes from
decimal to integer or another decimal, I get a Concurrency violation: the
UpdateCommand affected 0 records error.

I have used trace to view the CommandText and all the source columns and
parameters. When I try to execute the update statement directly in the
database, the record updates. Just a code issue, apparently. I noticed in a
search of these forums someone else had a similar problem, and they solved
it, but never posted their fix.

Any suggestions? using .NET 1.0 framework w/ ODP.NET data provider.
Click to expand...

Correction: The code is using Double not Decimal
 
Back
Top