FIX: OLE DB Provider for SQL Server Does Not Cancel a Batch Statement When You Call the Cancel() Method (325338)
The information in this article applies to:
- Microsoft OLE DB Provider for SQL Server 2000 2000.81.7713.0
- Microsoft OLE DB Provider for SQL Server 2000 2000.80.194
- Microsoft OLE DB Provider for SQL Server 2000 2000.80.380.0
- Microsoft OLE DB Provider for SQL Server 7.0
This article was previously published under Q325338 SYMPTOMS
When you call the Cancel method on an ADO Connection or Recordset object, Microsoft OLE DB Provider for SQL Server (SQLOLEDB) does not cancel a query that is asynchronously executed and that involves a batch statement. Instead, Microsoft OLE DB Provider for SQL Server calls the SQLMoreResults method to fetch the remaining results.
CAUSE
This problem occurs because of a code problem in which OLE DB Provider for SQL Server calls SQLMoreResults.
RESOLUTION To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Version Size (in bytes) File Name
----------------------------------------------------------------
27-Jun-2002 2000.81.9001.8 450,560 Sqloledb.dll
NOTE: This hotfix is for Microsoft Data Access Components (MDAC) version 2.7 only. If you are using an earlier version of MDAC, you must upgrade your MDAC version to 2.7 before you apply this hotfix.
WORKAROUND
There is no workaround for this problem if the query includes a batch statement.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.
Modification Type: | Minor | Last Reviewed: | 9/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbSQLServ2000sp3fix kbbug kbfix kbSQLServ2000preSP3fix KB325338 |
---|
|