Stored Procedure Question

OK, so I found what I think is the issue... You need to add your DB's version of SET NOCOUNT ON (that's SQL Server syntax) in your procedure because if you don't , you'll return two datasets - the number of rows affected and then the data you're expecting. I found that here and remembered that I myself have done this before...

1 Like