1201) 12/8/2001 Q308401Q308401  Q308401.html">FIX: SQLExecute on a Prepared Statement with SQL_NOSCAN_ON Causes Client-Side AV (Q308401)
When you execute a statement that was prepared with the SQL_ATTR_NOSCAN attribute, you may receive an access violation (AV) as follows:

1202) 12/8/2001 Q311505Q311505  Q311505.html">BUG: "PL/SQL Argument Name Is Invalid" Error Message When You Use MSDAORA with 30 Character Parameter (Q311505)
When you use Microsoft OLE DB Provider for Oracle (MSDAORA) to run a stored procedure that takes parameters of 30 characters in length, you receive the following error message:

1203) 12/8/2001 Q304329Q304329  Q304329.html">FIX: Application Using Microsoft Oracle ODBC Driver Crashes When TNS Does Not Exist (Q304329)
When connecting with an ODBC connection (with or without a data source name) using the Microsoft ODBC driver for Oracle, if the specified Transparent Network Substrate (TNS) name does not exist for the Oracle server, an application may rece

1204) 12/8/2001 Q301953Q301953  Q301953.html">SQLOLEDB: Unenlisting From Active Transaction Against SQL Server 7.0 Causes Hang and Drain Abort Entry (Q301953)
When using the SQL Server native provider (SQLOLEDB) against a SQL Server 7.0 database, and when running in a transactional context such as MTS or COM+, directly or indirectly releasing an OLE DB session object that is enlisted in a distrib

1205) 12/8/2001 Q302995Q302995  Q302995.html">FIX: Memory Leak in MDAC SQLOLEDB Provider on SERVERDATAONINSERT and Column Size That Is Larger Than 255 (Q302995)
A memory leak occurs in Microsoft OLE DB Provider for SQL Server (SQLOLEDB) with SERVERDATAONINSERT when the column size is larger than 255.

1206) 12/8/2001 Q302248Q302248  Q302248.html">FIX: SQLOLEDB Does Not Work with DBACCESSOR_OPTIMIZED Flag and SSPROP_ENABLEFASTLOAD (Q302248)
Using the Microsoft OLEDB Provider for SQL Server (SQLOLEDB) that comes with Microsoft Data Access Components (MDAC) version 2.6 or 2.6 SP1, when you set the value of the SSPROP_ENABLEFASTLOAD property to true in the SQLSERVERDATASOURCE pro

1207) 12/8/2001 Q303446Q303446  Q303446.html">FIX: SQLOLEDB Returns No Data When Using AutoFetch Option with Fast Forward Cursors (Q303446)
The SQL Server native provider (SQLOLEDB) may return no data for a VARCHAR field that is larger than 255 characters under the following conditions:

1208) 12/8/2001 Q299765Q299765  Q299765.html">FIX: SQL Server 2000 ODBC Driver Fails to Return SQL Server 7.0 Server Names (Q299765)
From a client computer that has Microsoft Data Access Components (MDAC) 2.6 and SQL Server ODBC Driver version 2000.80.194, if you try to retrieve all of the server names by calling the

1209) 12/8/2001 Q300420Q300420  Q300420.html">FIX: Connection to SQL Server Database Using IP Address Is Unusually Slow (Q300420)
When Microsoft Data Access Components (MDAC) version 2.6 is installed, each attempt to connect to a SQL Server 7.0 or SQL Server 2000 database using an IP address (rather than the server name) may take longer than anticipated. In certain re

1210) 12/8/2001 Q297035Q297035  Q297035.html">FIX: Correlation Error Using Parameters.Refresh with SQLOLEDB (Q297035)
When executing a parameterized UNION query with the SQLOLEDB OLEDB Provider, the following error may be reported:

1211) 12/8/2001 Q313011Q313011  Q313011.html">PRB: Jet Memory Usage Increases When You Insert New Records (Q313011)
When you use the OLE DB Provider for Jet to insert records into a Microsoft Access database file, if you use the

1212) 12/8/2001 Q190743Q190743  Q190743.html">PRB: ADODB.Recordset Error '800a0bb9' When Using Boolean Filter (Q190743)
When you try to filter records based on a Boolean field on Active Server Pages (ASP) pages that the Dataform Wizard generates, you receive the following error message when you click

1213) 12/8/2001 Q308037Q308037  Q308037.html">FIX: ADO GetValue Does Not Check DBSTATUS_S_ISNULL for VARIANT (Q308037)
When using ActiveX Data Objects (ADO) against certain OLE DB providers, you may find that recordset fields that should be NULL do not test for NULL correctly either by checking the VARIANT.vt value for VT_NULL (in Microsoft Visual C++) or b