226) 5/25/2012 185823 BUG: MS Access ODBC Driver Does Not Expose adFldIsNullable to ADO
(185823) - When using Microsoft ActiveX Data Objects (ADO) with the Microsoft Access ODBC driver, attempts to programmatically check the nullability of a field with the ADO Field "Attributes" property, returns True even if the field is a required (non-nullable)... 227) 5/24/2012 328514 FIX: Binding an Output Parameter of an Oracle Stored Procedure to adBSTR Results in an Incorrect Value
(328514) - When you bind a varchar2 type output parameter of an Oracle stored procedure to adBSTR in a Microsoft ADO application, the value that Microsoft OLE DB provider for Oracle (MSDAORA) returns is incorrect. In a Microsoft Visual Basic application the... 228) 5/22/2012 230501 HOWTO: Compact Microsoft Access Database Through ADO
(230501) - Although ADO specification does not provide objects to compact Microsoft Access databases, this capability can be achieved by using the ADO extension: Microsoft Jet OLE DB Provider and Replication Objects (JRO). This capability was implemented for the... 229) 5/17/2012 271228 IIS 5.0: Unable to Obtain Data from Access Database Residing on Netware 5 Server Using ASP
(271228) - An Access database exists on a Netware 5 Server volume that is running only the TCP/IP protocol. When you use either Open Database Connectivity (ODBC) or OLE Provider for Jet, a error message appears that states that the file cannot be found. There... 230) 5/22/2012 197902 PRB: Jet 3.51 OLE DB Provider Is Not Installed With MDAC 2.1 or Later
(197902) - The "3706: ADO could not find the specified provider" error appears when you try to connect to an Access database through the Jet 3.51 OLE DB provider. 231) 5/23/2012 300216 HOW TO: Keep a Jet 4.0 Database in Top Working Condition
(300216) - Microsoft Jet is the database engine that is used by default by Microsoft Access. This article provides a list of best practices that you can use to help keep your Jet database in top working condition. This article addresses a database running both... 232) 5/22/2012 236952 PRB: Sort Order Has Changed with Microsoft Jet version 4.0
(236952) - Using Microsoft Jet version 4.0, sorting is different than in previous versions. For example, assume you have the following records in an Access table: FIELD1 W W- WB W-B In previous versions of the Jet database engine, issuing "SELECT * FROM Table1... 233) 10/12/2006 Q220598 PRB: SQL Distributed Query with MSIDXS Provider Needs Additional Quotes
(220598) - Performing the following distributed query with SQL Server 7.0 and Index Server 2.0 OLE DB Provider SELECT a.* FROM OpenRowset('MSIDXS','Web';''; '', 'Select Directory, FileName, size, Create, Write from SCOPE() where CONTAINS(' ' "Index Server"... 234) 9/4/2007 Q269597 PRB: Limitations of ADO Client Cursor and Data-Bound Controls with DB2OLEDB
(269597) - When an ActiveX Data Objects (ADO) application uses a client-side cursor with the Microsoft OLE DB Provider for DB2 (DB2OLEDB) to retrieve data from DB2 (MVS or OS/390), an empty read-only recordset may be returned. 235) 8/17/2006 Q245267 DOC: "OLEDB_SERVICES = -2" Does Not Disable Autoenlistment
(245267) - The "OLE DB 2.0 Readme" (olreadme.txt) file in the Microsoft Data Access SDK version 2.0 states that: "OLEDB_SERVICES = -2" disables OLE DB resource pooling and autoenlistment." Pooling is disabled, but not autoenlistment. 236) 9/19/2006 Q201905 BUG: Distributed SQL Update, Jet Provider may not Return Errors
(201905) - When using a SQL Server 7.0 distributed query, with the Jet 4.0 OLE DB Provider to update a row in a Microsoft Access .mdb file, the update may fail and you will see an error similar to the following: OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported... 237) 8/10/2006 Q171613 INFO: Retaining Transactions with Transaction Object
(171613) - This article explains the relationship of retaining transactions and transaction object. 238) 10/28/2006 Q173410 INFO: Server-Side Cursors Are Forced with More Than One Command Object
(173410) - The OLE DB Provider for ODBC may force the use of server-side cursors if both of the following conditions are true: The backend database server is Microsoft SQL Server. -and- More than one Command object exists within the same session object.... 239) 8/21/2006 Q245379 PRB: MS OLE DB Provider for Oracle Doesn't Support INNER JOIN Syntax with ODBC Escape Sequence
(245379) - When an INNER JOIN operation is performed on two or more tables with the ODBC Escape Sequence "{oj}" using the Microsoft OLE DB provider for Oracle, a syntax error, access violation, or DB_E_ERRORSINCOMMAND may occur. 240) 9/27/2007 Q300685 OLEDB Provider Error Message: The Conversation Was Deallocated with AP_ABEND
(300685) - The error "Conversation was Deallocated with AP_ABEND" occurs when you are running an application (or sending code from an Active Server Pages page) to connect via TCP/IP through SNA Server's OLEDB Provider for AS400/VSAM to an AS400. The application...
1
2
.... .... 12
13
14
15
[ 16 ]
17
18
19
20
.... .... 34
35
Previous Page
Page 16 of 35
Next Page
|