This article has been archived. It is offered "as is" and will no longer be updated.
This Readme file contains updated information for the entire Microsoft Visual Studio suite of developer tools. If you downloaded a Core service pack from the Internet, not all sections of this file apply to the updates you received. The fixed issues appropriate for the Core downloads are those listed in the Visual Studio section plus the sections for the products updated by your Core download.
The Microsoft Visual Studio 6.0 Service Pack 3 Readme contains the following sections:
PART 1: Overview and Installation
PART 2: Visual Studio
PART 3: Visual Basic
PART 4: Visual C++
PART 5: Visual FoxPro
PART 6: Visual InterDev
PART 7: Visual J++
PART 8: Visual SourceSafe
PART 9: File Versions
For the latest product information, see the Visual Studio Web site at:
For the latest year 2000 information regarding Microsoft products, see the Microsoft Year 2000 Readiness Disclosure and Resource Center Web Site located at:
You can also call 1-888-MSFT-Y2K within the United States, toll-free, or contact your local Microsoft subsidiary.
Please see the REFERENCES section below for more information about how to access the parts of this readme.
Microsoft Visual Studio
The following run-time issue has been fixed with Service Pack 3 and was also fixed with Service Pack 1:
Passing in an unallocated array for an out-only SAFEARRAY parameter to a late-bound method call will fail.
Data Tools Update
The following Year 2000 issue has been addressed and updated in Visual Studio Service Pack 3:
Oracle and Visual Studio Query Designer may interpret two-digit year dates differently - Depending upon a system's regional date setting, Oracle and the Query Designer interpreted two-digit dates differently, which could result in data loss. This has been addressed and updated in Service Pack 3. In the Grid pane, the Query Designer now passes only four-digit dates to Oracle databases. In the SQL pane, the Query Designer passes the user input, either two-digit dates or four-digit dates.
Detecting a Corrupted User Settings File
Visual Studio now detects corrupted user settings files and removes the corrupted files from your machine. When this occurs, Visual Studio displays the following message:
"Unexpected Error. Quitting."
The next time you start Visual Studio, a new user settings file is automatically created.
Euro Currency Symbol Support in Windows 95
For more information about euro currency symbol support in Microsoft operating systems or to download the Microsoft Windows 95 euro product update, see:
Microsoft Windows 98 and Windows NT 4.0 SP4 are already compatible with the euro currency symbol.
Internet Explorer-Related Fixes
Internet Explorer 5 and Visual Studio 6.0
Visual Studio 6.0 Service Pack 3 resolves issues you may have encountered when running Visual Studio 6.0 and Internet Explorer 5 on the same machine. If you have or intend to have Internet Explorer 5 and Visual Studio 6.0 on the same machine, upgrade to Visual Studio 6.0, Service Pack 3.
Internet Explorer Versions and HTML Editing
Selection works differently in the HTML editor for sited elements depending on which version of Internet Explorer you have installed. A sited element is any element that has a height or width, such as BUTTON.
With Internet Explorer 4.01, selection for sited elements works as follows:
The first click on an element makes it possible for you to edit the text within the element.
The second click on an element selects the element or places the cursor in the element.
Double-clicking an element selects the text block within the element.
With Internet Explorer 5, selection for sited elements works as follows:
The first click on an element selects the element.
The second click on an element makes it possible for you to edit the text within the element.
Double-clicking the element brings up the source code for the element.
NOTE: Selection for tables works the same as it did in Internet Explorer 4.01.
In addition, Internet Explorer 5 preserves white space better than Internet Explorer 4.01 when you switch between views in the editor.
Microsoft ActiveX Data Objects (ADO) Documentation
The Microsoft ActiveX Data Objects documentation has been updated. See the ADO section under Visual Basic (Part 3) for further information.
Microsoft Repository Fixes
The version of Microsoft Repository included in Service Pack 3 includes major performance improvements to the Repository engine. It also fixes the following issues:
223318 Microsoft Repository running against an international Microsoft SQL 7.0 server would not handle dates formats other than mm/dd/yy.
223320 When working with large sets of repository relationships, the Repository engine would return an error stating the object cache was full, instead of automatically flushing cached relationships to the database.
223322 The Repository engine would return an error if a named relationship were renamed with a name that was more than 260 characters.
223323 If a workspace contained more than 31 objects, the Workspace.Contents collection would only return the first 31.
223326 The Repository engine would return an out-of-memory error if the client attempted to set a property of the type SQL_CHAR.
In SQL 6.5-based repositories, Service Pack 3 prevents searching by date published in yy/mm/dd format. To search for a component in Visual Component Manager by date published, you must enter dates using four-digit years or in m/d/y format regardless of the date format setting of the SQL Server. Date searching against a SQL 7.0-based repository is not affected, and dates should be entered in the default format of the SQL Server.
Unable to edit files in Design View in German Microsoft® FrontPage 98.
HTML files could not be edited in Design View in the German Microsoft FrontPage 98 which shipped with Visual Studio 6.0. This issue is corrected in Visual Studio 6.0 Service Pack 3.
Record deletion causes loss of cursor position with ADO or Microsoft Access ODBC driver.
If you are using the MDAC 2.1 or MDAC 2.1 SP1 Access ODBC driver directly or in combination with ADO and the OLE DB Provider for ODBC, a record deletion causes the loss of the cursor position. Because the cursor position is left in an unpredictable position, your application may not function as expected which may result in the loss of data. For complete details about this issue, please see the following article in the Microsoft Knowledge Base:
A hot fix for this issue is available from the Microsoft Visual Studio Home Page. This issue will be addressed in a future service release of MDAC 2.1.
If you use MDAC_typ.exe to redistribute MDAC 2.1 or MDAC 2.1 SP1 with any application built with Visual Studio, you should also redistribute the hot fix. Any application deployed using the MDAC 2.1 Access ODBC or ADO technology should include the hot fix.
Because this issue is present in MDAC 2.1 and MDAC 2.1 SP1, it will be present on any system that has the retail version of Office 2000, Internet Explorer 5, or the version of MDAC 2.1 SP1 available as a Web download.
For more information about the Visual Studio 6.0 SP3 readme, please see the following articles in the Microsoft Knowledge Base:
230722 Visual Studio 6.0 SP3 Readme Part 1 - Overview and Installation
230726 Visual Studio 6.0 SP3 Readme Part 3 - Visual Basic
230727 Visual Studio 6.0 SP3 Readme Part 4 - Visual C++
230729 Visual Studio 6.0 SP3 Readme Part 5 - Visual FoxPro
230730 Visual Studio 6.0 SP3 Readme Part 6 - Visual InterDev
230731 Visual Studio 6.0 SP3 Readme Part 7 - Visual J++
230732 Visual Studio 6.0 SP3 Readme Part 8 - Visual SourceSafe
230733 Visual Studio 6.0 SP3 Readme Part 9 - File Versions