901) 7/24/2007 Q268062 FIX: MDAC 2.5 Configuration Dialog Appears After Every Restart (Q268062)
After you install Microsoft Data Access Components (MDAC) 2.5 on a Microsoft Windows 95/98 or Microsoft Windows NT 4.0 computer, a 902) 9/27/2007 Q240377 HOWTO: Ensure Jet 3.5 Is Installed Correctly (Part I) (Q240377)
This article details steps you can take to correct an installation problem with Microsoft Jet 3.51. It covers troubleshooting for DAO, ActiveX Data Objects (ADO), and ODBC access methods. 903) 8/8/2006 Q323032 BUG: Component Checker Cannot Find Files in \Program Files\Common Files\System Folders (Q323032)
If the 904) 9/27/2007 Q321415 An Access Violation Occurs in ADO Under Heavy Stress with .NET COM Interop or Java (Q321415)
In a Microsoft .NET program that uses ActiveX Data Objects (ADO) through COM interop, or in a Java program that uses ADO, an access violation may occur when you call the 905) 9/29/2007 Q247957 SAMPLE: Using DUPS.exe to Resolve DLL Compatibility Problems (Q247957)
The DLL Universal Problem Solver tool (DUPS.exe) is a sample that contains all the utilities documented in the January 2000 Microsoft Developer Network (MSDN) News article "The End of DLL Hell." Please review that MSDN article before readin 906) 9/30/2007 Q233539 HOWTO: Programmatically Reset the Compatibility Level Setting of SQL Server ODBC Driver Version 3.70 (Q233539)
Under some circumstances, it may be necessary or desirable to change the compatibility mode setting of version 3.70 of the SQL Server ODBC driver from SQL Server 6.5 to SQL Server 7.0. This article shows how to programmatically restore the 907) 10/1/2007 Q231812 HOWTO: Programmatically Set the Compatibility Level of the SQL Server ODBC Driver (Q231812)
This article describes how to set the compatibility level of version 3.70.0623 of the SQL Server ODBC driver (Sqlsrv32.dll) to SQL Server 6.5 compatibility mode. 908) 9/29/2007 Q234525 ACC: Running Stored Access Queries with Wildcards via ODBC May Return Incorrect Results (Q234525)
In a Microsoft Access Jet 3.5 909) 10/5/2006 Q305983 FIX: OLE DB Simple Provider Does Not Issue Notifications on the aboutToChangeCell and cellChanged Functions (Q305983)
When you call the 910) 8/5/2006 Q303911 XCCC: DBCS Characters in a Reply of Meeting Request Are Corrupted in OWA with Microsoft Data Access Components 2.6 (Q303911)
If you install Microsoft Data Access Components version 2.6 on an Exchange 2000 server, double-byte character set (DBCS) characters in the subject, location, and body part of a reply of meeting request may not display correctly when you use 911) 9/29/2007 Q304394 FIX: Oracle Driver Doesn't Sort SQLPrimaryKeys Result Set by Key Sequence (Q304394)
If you call the 912) 7/2/2007 Q286204 PRB: Slow CGI Performance with Microsoft ODBC for Oracle on Windows NT 4.0 (Q286204)
After installing Microsoft Data Access Components (MDAC) version 2.5 or later, the open and close performance of a single connection to the Microsoft ODBC for Oracle driver is noticeably slower. This impacts the performance of typical singl 913) 8/25/2007 Q270586 FIX: Syntax Error When You Use ODBC Canonical Date Format as Parameter to SQL Stored Procedure (Q270586)
When you pass an ODBC canonical date literal as a parameter to a SQL Server stored procedure using the Microsoft SQL Server ODBC driver, a syntax error may be reported: 914) 7/30/2007 Q264081 FIX: Incorrect Pre-1753 Date Values With Jet ODBC Driver (Q264081)
When the Microsoft Access ODBC Driver reads a date prior to 1753, the returned date is not consistent with the date actually stored in the database. When you use the Microsoft Access ODBC Driver to write dates prior to 1753, the stored dat 915) 10/26/2006 Q259691 FIX: Error Message "Invalid Time Format" When You Insert Date/Time With Maximum Values (Q259691)
When you use the Microsoft SQL Server ODBC driver and you use
1
2
.... .... 57
58
59
60
[ 61 ]
62
63
64
65
.... 75
Previous Page
Page 61 of 75
Next Page
|