BUG: You receive an incorrect number for affected rows when you run a stored procedure that inserts, updates, or deletes (313544)
The information in this article applies to:
- Microsoft ODBC for Oracle version 2.7 Build 2.573.7713.2
- Microsoft Visual Studio .NET (2002), Professional Edition
This article was previously published under Q313544 SYMPTOMS When you run a stored procedure that inserts, updates, or
deletes, you receive an incorrect number (-1) for the number of rows that are
affected.
This problem also occurs in Microsoft Visual Basic 6.0
applications that use the Microsoft ODBC for Oracle driver.
RESOLUTION To work around this problem, use the OLE DB managed
provider with Microsoft OLE DB Provider for Oracle.
For Visual Basic
6.0 applications that use the ODBC for Oracle driver, use Microsoft ActiveX
Data Objects (ADO) with Microsoft OLE DB Provider for Oracle. STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
REFERENCESFor additional information, click the article
number below to view the article in the Microsoft Knowledge Base: 309486 HOW TO: Execute SQL Parameterized Stored Procedures by Using the ODBC .NET Provider and Visual Basic .NET
The third-party products that are
discussed in this article are manufactured by companies that are independent of
Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the
performance or reliability of these products.
Modification Type: | Minor | Last Reviewed: | 9/15/2005 |
---|
Keywords: | kbvs2002sp1sweep kbbug kbpending KB313544 |
---|
|