1111) 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 1112) 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. 1113) 7/27/2007 Q238116 PRB: Accessing a Temporary SQL Server Table Results in a DB_E_NOTABLE (Q238116)
When using the SQL Server ODBC driver with forward-only server-side cursors in trying to access a local temporary SQL Server table that was explicitly created using the same ActiveX Data Object (ADO) connection object, the application rec 1114) 2/19/2007 Q231943 INFO: Microsoft Data Access Components (MDAC) Release History (Q231943)
This article outlines the different Microsoft Data Access Component (MDAC) versions available and the products that install them. 1115) 1/11/2007 Q308401 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: 1116) 9/29/2007 Q311505 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: 1117) 12/18/2006 Q302248 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 1118) 9/27/2007 Q308037 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
1
2
.... .... 67
68
69
70
71
72
73
74
[ 75 ]
Previous Page
Page 75 of 75
|