1006) 9/15/2007 Q225334 PRB: Jet/VBA May not Work Correctly w/ Datetime Data Containing Higher Precision for Fractional Seconds (Q225334)
In some cases, when running queries from Microsoft Access or any application that uses Jet/VBA, like Data Access Objects (DAO), that involve an ODBC timestamp or SQL datetime data with the fractional portion of the timestamp having a 1007) 2/2/2007 Q269238 INFO: Version List of the Microsoft XML Parser (Q269238)
This article lists the version numbers of Microsoft's Extensible Markup Language (XML) parser (Msxml.dll Msxml2.dll, Msxml3.dll, and Msxml4.dll) and the Microsoft products that include this component. 1008) 8/7/2006 Q271619 HOWTO: Retrieve XML Data by Using an XPath Query in a Visual Basic Client (Q271619)
This article demonstrates how to programmatically retrieve an XML data stream from a SQL Server 2000 mapping schema by using an XPath query. The scope operates in a client/server (2-tier) model. 1009) 3/19/2007 Q297997 PRB: MSXML Performance Bottleneck in ShareMutex Under Stress (Q297997)
When you use XML (Msxml3.dll) in a high-stress environment such as Microsoft Internet Information Server (IIS), a bottleneck can occur around the 1010) 6/7/2006 Q298961 FIX: No Error Message When XML Malformed File Opened in Internet Explorer on Windows 95/98/Me Systems (Q298961)
When you use Microsoft Internet Explorer to open an XML file that has no encoding specified and that contains characters with high ASCII-codes, and your computer is running Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows M 1011) 9/5/2007 Q230496 HOWTO: Compacting Microsoft Access Database Through OLE DB (Q230496)
OLE DB specification doesn't provide interfaces to compact or repair databases. However, the OLE DB Provider for Microsoft Jet version 4.0 exposes this functionality through a custom interface: IJetCompact (TDataSource cotype). IJetCompact 1012) 11/22/2006 Q244661 INFO: Limitations of Microsoft Oracle ODBC Driver and OLEDB Provider (Q244661)
This article lists the limitations of the current version of Microsoft ODBC driver and OLE DB Provider for Oracle. 1013) 10/15/2006 Q251254 PRB: "Disk or Network Error" or "Unspecified Error" Returned when Using Jet (Q251254)
When trying to connect to an Access .mdb file, an ODBC error is returned stating "Disk or Network Error". The Microsoft OLE DB Provider for the Microsoft Jet database engine may also return an "Unspecified error" (error code = 0x80004005) m 1014) 9/29/2007 Q250999 PRB: RDS Does Not Work Correctly with OLE DB Simple Provider (Q250999)
When the Remote Data Service (RDS) for ActiveX Data Objects (ADO) is used with an OLE DB provider that was built by using the OLE DB Simple Provider (OSP) Toolkit, the following error message may occur: 1015) 1/16/2007 Q258576 INFO: Limitations of IRowsetIndex::Seek() Used with Jet database (Q258576)
You can use 1016) 5/31/2007 Q267550 BUG: "Assertion Failed" When You Connect to a SQL Server Through TCP/IP (Q267550)
When you attempt to connect to a SQL Server through TCP/IP on a Windows 98 client, the following error message can occur: 1017) 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: 1018) 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. 1019) 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. 1020) 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
.... .... 64
65
66
67
[ 68 ]
69
70
71
72
.... 75
Previous Page
Page 68 of 75
Next Page
|