FIX: Second SQLExecute on Prepared Statement with SQL_NOSCAN_ON Causes Client-Side AV (295757)
The information in this article applies to:
- Microsoft Data Access Components 2.6
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q295757 SYMPTOMS
On an ODBC connection to a SQL Server 2000 server, the second call to the SQLExecute function on a prepared statement may cause a client-side access violation (AV) if the statement attribute SQL_ATTR_NOSCAN is set to SQL_NOSCAN_ON prior to execution.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack
Hotfix
The English version of this fix should have the following file attributes or later:
Date Version Size File name Platform
--------------------------------------------------------------
11/13/2000 2000.80.221.0 471,119 Sqlsrv32.dll x86
11/13/2000 2000.80.221.0 28,742 Odbcbcp.dll x86
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 Data Access Components 2.6 Service Pack 1.
| Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbMDAC260sp1Fix kbQFE KB295757 |
|---|
|