91) 3/18/2010 183565 Underlyingvalue Property Incorrect for Certain Characters
(183565) - The ADO property Underlyingvalue is often incorrect, generally with 8-bit ASCII characters. For example, ASCII character #162, the "cents" symbol, appears as o with a forward-accent in the underlying value property. 92) 3/10/2010 183558 Conformance to ADO 2.0 and OLE DB 2.0
(183558) - This is a list of nonconformance problems that may occur: IDBProperties->GetPropertyInfo is not level 0 compliant for certain properties. IOpenRowset::OpenRowset gives incorrect results when rgPropertySets = NULL and cPropertySets <> 0.... 93) 3/9/2010 183560 OpenSchema Method Fails for DBSCHEMA_PROVIDER_TYPES
(183560) - The OpenSchema method does not return any information for DBSCHEMA_PROVIDER_TYPES. The ADO OpenSchema method does not result in any errors, but it does not provide any information either. 94) 3/8/2010 183554 Incorrect Error Message When Data Source Is Missing
(183554) - When you provide a connect string that contains a data source name for which there is no actual data source, the resulting error message indicates an SNA Server LU alias name is incorrect, for example: Microsoft SNA OLE DB Provider (ODB) -2147467259... 95) 2/26/2010 183551 Unable to Locate Host Column Description File
(183551) - By default, a Host Column Description (HCD) file is placed in the ..\sna\system subdirectory when it is created using the Microsoft Management Console (MMC) administration snap-in tool. If the HCD file is subsequently moved to another directory, the... 96) 3/18/2010 183550 Administrative Snap-in Allows Duplicate Names for HCD Files
(183550) - Using the administrative tool snap-in in the Microsoft Management Console (MMC), you can create two identically named Data Description Files (host column definition files, HCD files). (One physical file, so-named and having an .hcd extension, appears... 97) 3/19/2010 235521 BUG: Configuring a Data Link for OLE DB Provider for AS/400 and VSAM Fails
(235521) - If you install SNA Server or Client 4.0 Service Pack 2 with only the Microsoft OLE DB provider for AS/400 and VSAM selected and not the Microsoft OLE DB provider for DB2, and you configure a new Microsoft data link to use the Microsoft OLE DB provider... 98) 3/18/2010 259753 FIX: Deadlock in OLE DB Session Pooling in an STA COM Object
(259753) - When you use OLE DB session pooling from a single threaded apartment (STA) COM object on a Windows NT 4.0 computer, STA COM object method re-entrancy may cause a deadlock in the OLE DB synchronization code. 99) 3/2/2010 191746 HOWTO: Use ATL Consumer Classes to Connect to SQL Server
(191746) - This article demonstrates how to use ATL Consumer Classes with the SQLOLEDB provider to connect to SQL Server 6.5, 7.0, and 2000. 100) 3/10/2010 275630 INSERTS from DTS to DB2 Through OLE DB Provider for DB2 May Not Work Correctly
(275630) - If a DTS package is built to export a SQL Server table to DB2/MVS (version 5.1) by using the Microsoft OLE DB Provider for DB2 (DB2OLEDB) and the AUTOCOMMIT property of the provider is set to FALSE, the following error may be reported: [OLE/DB... 101) 3/10/2010 278242 DB2OLEDB Provider Incorrectly Maps Isolation Levels
(278242) - If the Microsoft OLE DB Provider for DB2 parameter for Default Isolation Level is set to Cursor Stability (CS), it could be incorrectly mapped by the provider as Repeatable Read (RR) on DB2. This may lead to the incorrect type of locks being held on... 102) 3/14/2010 304536 FIX: "Object invalid or no longer set" Error with Microsoft Jet
(304536) - When opening and closing connections or recordsets using the Microsoft ODBC Driver for Access or the Microsoft OLE DB Provider for Jet, the following error may be reported: Object invalid or no longer set. After this error is reported, no more... 103) 3/17/2010 216519 PRB: SQL Server 6.0 Does Not Work with SQLOLEDB Provider in a SQL Server 7.0 Distributed Query
(216519) - The SQLOLEDB provider returns the following error message when accessing a SQL Server 6.0 in a SQL Server 7.0 distributed query: Server: Msg 7399, Level 16, State 1, Line 1 OLE DB provider 'SQLOLEDB' reported an error. [OLE/DB provider returned... 104) 3/2/2010 191870 INF: Poor Response Time Returning Multiple Mainframe Records
(191870) - When a consumer or client program, using ADO, asks for multiple records from an IBM OS/390 VSAM file, the response time is very slow and increases with the number of records retrieved. To improve the response time, set the CacheSize property of the... 105) 3/11/2010 183569 AS/400 RDB Name Cannot Exceed Eight Characters
(183569) - The RDB Name property of an AS/400 data source allows only eight characters to be entered in the edit box. However, these names can be up to 16 characters long.
1
.... 3
4
5
6
[ 7 ]
8
9
10
11
.... .... 34
35
Previous Page
Page 7 of 35
Next Page
|