481) 9/23/2007 Q269344 BUG: Microsoft Oracle ODBC Driver and OLE DB Provider Report "Driver Not Capable" (Q269344)
When attempting to enlist in a distributed transaction by using either the Microsoft ODBC for Oracle or the Microsoft OLE DB Provider for Oracle, the following error message occurs: 482) 8/22/2006 Q269412 FIX: Access Violation Occurs When You Call SQL Server Stored Procedure That Contains PRINT Statement (Q269412)
An access violation occurs when you call a SQL Server stored procedure that contains a PRINT statement that displays a string containing approximately 700 characters. 483) 9/24/2007 Q271128 PRB: Implicit Connections Created by the SQL Server OLE DB Provider (SQLOLEDB) Are Not Pooled (Q271128)
When the Microsoft OLE DB Provider for SQL Server (SQLOLEDB) creates implicit connections, these connections are not pooled. 484) 9/24/2007 Q271524 PRB: Oracle Synonyms Associated with Database Links Not Listed by OLE DB Provider or ODBC Driver (Q271524)
The Microsoft OLE DB Provider for Oracle and the Microsoft ODBC driver for Oracle do not display Oracle synonyms that are associated with database links created for remote database objects. 485) 1/19/2007 Q272358 PRB: SQLOLEDB Allows Only One Connection in Scope of Transaction (Q272358)
With the Microsoft OLE DB Provider for SQL Server (SQLOLEDB), when you try to run multiple commands in the same session within the scope of a transaction, you may receive the following error message: 486) 6/9/2007 Q271774 SAMPLE: How To Manipulate the "Trustee PIN" Jet Property Using ADOX in VC (Q271774)
ADOX.exe demonstrates the use of the 487) 8/16/2006 Q271908 INFO: MDAC Version 2.6 and Later Do Not Contain Jet or Desktop ODBC Drivers (Q271908)
Starting with Microsoft Data Access Components (MDAC) version 2.6, MDAC no longer contains Jet components. In other words, MDAC 2.6 and 2.7 do not include Microsoft Jet, Microsoft Jet OLE DB Provider, and the ODBC Desktop Database Drivers. 488) 6/28/2007 Q277033 FIX: SQL_BIGINT in 2.x ODBC Driver Is Mapped to SQL_C_SBIGINT 3.0 Datatype (Q277033)
When the Microsoft OLEDB Provider for ODBC driver (MSDASQL) is using an ODBC driver that is ODBC 2.x compliant, and the driver reports a SQL_BIGINT datatype (-5), the ODBC provider (MSDASQL) chooses a C datatype of SQL_C_SBIGINT for use in 489) 9/26/2006 Q279245 FIX: Default Column Properties Cleared When You Set or Check Values by Using ADOX to an Access Database (Q279245)
When you set or check the default column values for any column in a table that is contained in an Access 2000 database, the default values for the column are cleared. 490) 1/10/2007 Q283842 FIX: IN and UNION Clauses Produce Incorrect Column Count (Q283842)
With the Microsoft OLE DB Provider for Oracle (MSDAORA), the execution of a SQL statement that contains both an IN and a UNION clause may produce an ActiveX Data Objects (ADO) 491) 9/23/2007 Q286189 HOWTO: Invoke the OLE DB Data Link Properties Dialog Box in Visual Basic Code (Q286189)
The 492) 1/17/2007 Q289278 PRB: Setting DBPROP_REMOVEDELETED Property to VARIANT_FALSE Fails to Open Fast-Forward Cursor (Q289278)
SQL Server 2000 Books Online contains a section titled "Rowsets and SQL Server Cursors" which states that setting the following rowset properties for the SQL Server OLE DB Provider (SQLOLEDB) is equivalent to a fast-forward cursor: 493) 9/27/2007 Q291999 PRB: DB2 Stored Procedures on OS390 Return Invalid Parameter Information (Q291999)
When run against an IBM DB2 database that is installed on an OS390 server, 494) 9/26/2007 Q293349 PRB: Retrieving Properties with OLE DB May Cause Memory Leak (Q293349)
Whenever an OLE DB consumer application retrieves properties from the provider, it is the responsibility of the consumer application to free the memory associated with the property structures that the provider returns. 495) 9/29/2007 Q293658 HOWTO: Force Query-Based Updates with ADO and MSDASQL (Q293658)
When you use ActiveX Data Objects (ADO) with the Microsoft OLEDB Provider for ODBC Driver (MSDASQL), and you try to update a table using a server-side cursor, ADO uses positioned update by default. In this case, the MSDASQL provider calls t
1
2
.... .... 27
28
29
30
31
32
[ 33 ]
34
35
Previous Page
Page 33 of 35
Next Page
|