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..
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

ExecuteNonQuery returning -1 1
ODP.NET ExecuteNonQuery Affected Rows Problem 1
SQLCommand.ExecuteNonQuery returns wrong number 5
Number of rows affected for OleDbCommand.ExecuteNonQuery 3
Getting double count of updated records 3
Retrieving Rows Affected Counts 16
Problem with ExecuteNonQuery() Result, Access, ASP.NET, C#, ADO, OleDB 7
ExecuteNonQuery 3

Back
Top