EmbersFire (embers_fire (AT) fastmail (DOT) fm) writes:
Quote:
I'm using a stored proceedure which should update a number of rows in a
table depending on a key value supplied (in this case 'JobID'). But
what's happening is when I call the proc from within the program, only
one row gets updated.
So
When I call the proc from Query Analyser, all rows get updated.
When I call the proc from within the program, only one row gets updated |
That's funny. A SET ROWCOUNT in effect sounds like the most like, but
it appears that you have already ruled this out.
Could there be trigger on the table? (Although that would be a strange
trigger.)
One thing, though:
Make this
.Execute ,,adExecuteNoRecords
this can save you from a few funny surprises in other situations. Use
this option whenever you run a command that does not generate any result
set.
And have you double-checked that you run the VB-app against the same
database as you run QA? And have you made sure that there is only one
instance of the table and the stored procedure?
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp