ExecuteNonQuery returns wrong number of records affected.

  • Thread starter Thread starter Vince Varallo
  • Start date Start date
V

Vince Varallo

Hello All,

I am using the command.ExecuteNonQuery() method to execute
an update statement. I then check the return value to see
how many records were affected by the update. This used
to work in .NET 1.0, but when we upgraded to .NET 1.1 it
now returns -1. Has anyone else experienced this?

Thanks in advance,
Vince
 
Are you sure you didn't set NO COUNT off or something?
I work with 1.1 and it works great..
 
Back
Top