Microsoft Visual Studio 6.0 Service Pack 4 Readme

© 2000 Microsoft Corporation. All rights reserved.

Note   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 4 Readme contains the following sections:

1. Finding More Information

For more in-depth information and for the latest Product Support information about the Visual Studio issues that are fixed in this Service Pack, see http://support.microsoft.com/support/vstudio.

For the latest product information, see the Visual Studio Web site at http://msdn.microsoft.com/vstudio.

2. File Versions

The file list details the files that have been provided in this Visual Studio 6.0 Service Pack by filename, date, version number, and path on the Service Pack 4 CD. See Determining the files that Setup installs for more information about determining if a file on your system is the SP4 version.

3. Overview

The Microsoft Visual Studio 6.0 Service Pack 4 addresses known issues with Visual Studio 6.0. These fixes are categorized as:

In addition, this service pack addresses known binary-compatibility bugs with certain run-time redistributable files in Visual Studio 6.0. This service pack also provides the source files and debug versions of the Microsoft® Visual C++® run-time components for Visual C++ developers.

The Microsoft Visual Studio 6.0 Service Pack 4 includes all of the fixes in Service Packs 1, 2, and 3 and updates the following Visual Studio applications:

In addition, this service pack includes updated or upgraded versions of:

4. Installation

Install this service pack whenever you have updated or changed any of the applications in Visual Studio to ensure that you have the latest fixes. Any open applications should be shut down before installing this service pack.

To install from an Internet download

  1. See the Microsoft Visual Studio Home Page.
  2. Run SetupSP4.exe from your download extraction folder.

To install from CD-ROM

Setup will detect the language of your computer's operating system and automatically run one of the following setups:

\chs\SetupSP4.exe (Simplified Chinese)
\cht\SetupSP4.exe (Traditional Chinese)
\deu\SetupSP4.exe (German)
\enu\SetupSP4.exe (English)
\esp\SetupSP4.exe (Spanish)
\fra\SetupSP4.exe (French)
\ita\SetupSP4.exe (Italian)
\jpn\SetupSP4.exe (Japanese)
\kor\SetupSP4.exe (Korean)

If your operating system language setting is not in this list, the English version of Setup will run.

Note   Service pack files are available on individual CD-ROMs. Each CD-ROM includes a set of languages.

The following language sets are available on individual CD-ROMs:
English, Spanish, French
English, Italian, German
English, Simplified Chinese, Traditional Chinese, Korean
English, Japanese.

Refreshing the common directory setting

Under certain circumstances, the installation setting for the Visual Studio common directory can become damaged, which prevents the Service Pack Setup from updating files on your system. If the Service Pack Setup cannot find the common directory setting, it will alert you.

If you see this dialog box, refresh the directory setting by installing or reinstalling any Visual Studio product before installing the service pack. If you already have a Visual Studio product installed, reinstalling the product provides the quickest resolution.

To reinstall

  1. Open Control Panel.
  2. Choose Add/Remove Programs.
  3. Select the Install/Uninstall tab.
  4. Select Visual Studio 6.0.
  5. Choose Add/Remove.
  6. When Visual Studio Setup starts, select Reinstall to repeat the last installation and restore missing files and settings.

4.1. Visual Studio 6.0 Service Pack 4 requirements

The following products are required for this service pack:

The following products are strongly recommended for this service pack:

Specific product installation requirements

Some Visual Studio 6.0 products have specific installation requirements for Service Pack 4. Click one of the following product names to view its specific installation requirements.

4.2. Installing Microsoft Data Access Components 2.5

Microsoft Data Access Components (MDAC) 2.5 is required for Visual Studio 6.0 Service Pack 4. If you do not have MDAC 2.5 installed, you must install it before installing the service pack. The Service Pack Setup will inform you if you must install MDAC 2.5.

Because MDAC 2.5 is a system component, you must install a language version matching your system's language setting. If you inadvertently install a language version that does not match your system's language setting, reinstall the appropriate MDAC 2.5 for your system's language setting.

To install MDAC 2.5

If MDAC 2.5 Setup requests that you restart your computer, you must do so and then restart Visual Studio Service Pack 4 Setup (SetupSP4.exe).

Note    In the Spanish version, the file MDAC_TYP.EXE may not get updated to the proper version in the following directories:

\Common\IDE\IDE98\redist
\vb98\wizards\pdwizard\redist\, and
\vfp98\distrib.src\system\.

This is due to the external version number for the Spanish MDAC. Check the version number for MDAC_TYP.EXE in the above directories. If it is not 25.0.4403.12, manually copy the file from the install CD to the proper location.

Installing the MDAC 2.5 library and header files

To use the MDAC 2.5 headers and libraries you must install the latest Platform SDK and check your INCLUDE and LIB paths to make sure that the correct files are being used. The latest Platform SDK is available at http://msdn.microsoft.com/downloads/sdks/platform/platform.asp.

4.3. Installing different language versions of the service pack

Each time Setup is run, only those files matching the setup language are updated. If you have installed different Visual Studio 6.0 products in different languages, you must run the appropriate SetupSP4.exe for each product's language to install Service Pack 4.

4.4. Determining the files that Setup installs

Setup might not install all the files included in this Service Pack on your computer. If you do not have a copy of the file on your computer or if the file on your computer is a more recent version than the one in the Service Pack, Setup will not update the file on your computer.

Setup might not update files, such as text files and non-binary files, that you have previously modified. Setup primarily determines which files to replace by checking the version information in a file's resources. However, some files, such as text files and non-binary files, have no resource information. In these cases, Setup uses the date/time stamp to determine which files must be replaced.

If the date/time stamp on any Visual Studio file that does not have version information is more recent than the file that shipped with Service Pack 4, then Setup might not replace those files. Source files, header files, and .ini files are examples of some files that might have a later date.

4.5. Determining the update history of products

To determine which updates have been made since the initial release of a product, you must examine the version number in the properties of one or more files.

To determine the update status of a product:

  1. Look in the file list at the end of this Readme file to determine which file you want to examine. In some cases, you might need to examine more than one file to fully determine the product's update history.
  2. For each file, right-click the file in Windows Explorer, and then choose Properties.
  3. Select the Versions tab and compare the version listed with the version in the table.

4.6. Uninstalling the Visual Studio 6.0 Service Pack

The Service Pack cannot be uninstalled independently of Visual Studio.

4.7. Known issues

4.7.1. Windows 95 Registry size limitation

A 64 KB limitation in the size of the SharedDLL key in the Windows 95 system registry might generate a warning during installation. This issue does not affect Windows 98, Windows NT, or Windows 2000 systems. To work around this issue:

After taking one or more of these actions, run Visual Studio 6.0 Service Pack 4 Setup (SetupSP4.exe) again.

4.7.2. Installing Internet Explorer 5 on Windows 95

While installing Internet Explorer 5 on Windows 95, you might receive the following error: "A previous program installation was never completed. You need to restart your computer to complete that installation before running Internet Explorer Setup. Setup will now close." To work around this error, restart your computer, leaving the Service Pack 4 CD-ROM in the drive. You can then successfully install Internet Explorer 5.

4.7.3. Installing Office 2000 SR1

If you install Office 2000 SR1 and then install Windows NT Options Pack, msdatsrc.tlb regresses to an earlier version. To resolve the problem, reinstall Office 2000 SR1 after you install Windows NT Options Pack.

4.7.4. Overwritten C2.DLL

C2.dll will be overwritten with the SP4 version even if the file is marked read-only.

4.7.5. Missing STF Files

If a product's SETUP.STF file is missing when you install Service Pack 4, then that product's files will not be updated.

For a US English language Visual Studio 98 installation, the file should be at C:\Program Files\Microsoft Visual Studio\Common\Setup\1033\setup.stf by default. For a Visual FoxPro 6 standalone installation, this should be C:\Program Files\Microsoft Visual Studio\VFP98\Setup\1033\setup.stf. The directory containing the stf file will be named with a different 4 digit number depending on localization. If the stf file is missing, the setup will appear to proceed normally and without error. Some common files like ActiveX control OCX files will be updated, but the individual products, like Visual Basic 6 or Visual FoxPro 6 will not be updated. To work around this, copy the file sp498ent.stf from the root SP4 source directory, to the directory which should contain the stf. Rename the copied file setup.stf, and rerun the Service Pack 4 install program setupsp4.exe. This should allow the installed VS98 products to be updated to Service Pack 4.

4.7.6. Updated Merge Modules

Service Pack 4 includes updated versions of Merge Modules (.msm files) for use with Visual Studio Installer or other Windows Installer authoring tools. These files are not installed during setup, you must copy them from the Service Pack 4 CD-ROM to the \Microsoft Visual Studio\Common\Tools\Vsinst\Buildres directory.

Some of the updated Merge Modules may contain versions of some system files that are newer than the versions shipped with Windows 2000. Due to the Windows File Protection feature of Windows 2000, these newer versions of the files cannot be installed on Windows 2000. Because of this, the Merge Modules are set up not to attempt to install these newer versions on Windows 2000 (although they will be installed on other operating systems).

If you use one or more of these Merge Modules in a Visual Studio Installer project on a Windows 2000 machine, you will get a warning in the task list that "One more files in <merge module> have different versions than those installed on this machine".

You can safely ignore this warning in almost all cases, as the differences between the versions of the system files in the Merge Modules and those included in Windows 2000 are minor. Almost all applications that use these files will operate properly with the file versions that shipped with Windows 2000. The file versions contained in the Merge Modules will also be included in a future service pack for Windows 2000.

4.7.7. Installing SP4 on Windows 2000

If you are installing SP4 on Windows 2000, you must use a release version of Windows 2000. SP4 will not function properly on a Beta or Release Candidate version of Windows 2000.

4.7.8. Installing using Terminal Server

If you install Windows 2000 Server with Terminal Server and then install Visual J++ 6.0, the following message results: ""A terminal server must be in install mode before you can install a program." Change to install mode and install Visual J++ 6.0. Restart when you are prompted. After you restart and return to Terminal Server, change to install mode and install SP4.

5. Notes on Fixes

The Microsoft Visual Studio 6.0 Service Pack 4 includes all of the fixes in Service Packs 1, 2, and 3.

5.1. Microsoft Visual Studio

5.1.1. Automation fix

5.1.1.1. Fixed in Service Pack 3:

The following run-time issue has been fixed as of Service Pack 3:

5.1.2. Database Tools update

5.1.2.1. Fixed in Service Pack 4:

5.1.2.2. Fixed in Service Pack 3:

Known issue

5.1.3. Detecting a corrupted user settings file

5.1.3.1. Fixed in Service Pack 3:

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.

5.1.4. 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 http://www.microsoft.com/windows/euro.asp. Microsoft Windows 98 and Windows NT 4.0 SP4 are already compatible with the Euro currency symbol.

5.1.5. Internet Explorer-related fixes

5.1.5.1. Fixed in Service Pack 3:

Internet Explorer 5 and Visual Studio 6.0

Visual Studio 6.0 Service Pack 4 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 4.

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:

With Internet Explorer 5, selection for sited elements works as follows:

In addition, Internet Explorer 5 preserves white space better than Internet Explorer 4.01 when you switch between views in the editor.

5.1.6. Microsoft ActiveX Data Objects (ADO) documentation

5.1.6.1. Fixed in Service Pack 3:

The Microsoft® ActiveX® Data Objects documentation has been updated. See the ADO section under Visual Basic for further information.

5.1.7. Microsoft Repository fixes

5.1.7.1. Fixed in Service Pack 3:

The version of Microsoft® Repository included in Service Pack 4 includes major performance improvements to the Repository engine. It also fixes the following issues:

Known issue

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.

5.1.8. Miscellaneous fixes

5.1.8.1. Fixed in Service Pack 4:

5.1.8.2. Fixed in Service Pack 3:

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.


5.2. Microsoft Visual Basic

Microsoft® Agent 2.0

Microsoft Agent, which shipped with Visual Studio 6.0 and Visual Basic 6.0, has a new release on the Internet. You can download Agent 2.0 royalty-free from the Microsoft Agent Web site, where you will also find the updated Agent SDK, including documentation, HTML and code samples, and licensing information.

Visual Studio Installer

Visual Studio Installer is an add-in for Visual Studio 6 that allows you to create Windows Installers (also known as Setup programs) for your Visual Basic applications. It can be used to create installers for Windows 9x, Window NT 4.0, and it is the preferred method for Windows 2000. You can download the latest version of Visual Studio Installer royalty-free from the Microsoft Visual Studio Web site.

5.2.1. Installation information

Setup updates files that are not versioned, such as text files and nonbinary files, based on the date of the file. If you have previously modified one of these files and the date/time stamp is more recent than the date/time stamp on the file included with Service Pack 4, Setup will not update the file. One likely file in this category is vb6dep.ini. For additional information, see Determining the update history of products based on file versions.

5.2.2. Controls issues

5.2.2.1. Fixed in Service Pack 4:

The following control issues have been fixed.

5.2.2.2. Fixed in Service Pack 3:

The following Controls issues have been fixed:

5.2.3. International product issues

5.2.3.1. Fixed in Service Pack 3:

The following international product issues have been fixed:

5.2.4. Microsoft ActiveX Data Objects (ADO) documentation

5.2.4.1. Fixed in Service Pack 3:

Updated Microsoft ActiveX Data Objects (ADO) documentation is installed with this Service Pack. All users may access the updated ADO 2.1 documentation (ado210.chm) from the Help folder in their Windows directory. Visual Basic users will have access to this documentation through context-sensitive (F1) help if they have installed Microsoft Data Access Components 2.1 and created a reference to the Microsoft ActiveX Data Objects 2.1 library.

To create a reference to the ADO 2.1 library:

  1. From the Project menu, select References.
  2. Ensure "Microsoft ActiveX Data Objects 2.1 Library" is selected.
  3. Click OK.

Context-sensitive help is available for all ADO 2.1 objects, collections, methods, and properties. Pressing F1 calls the standalone ADO 2.1 help, not the MSDN™ library.

5.2.5. Package and Deployment Wizard issues

5.2.5.1. Fixed in Service Pack 4:

The following Package and Deployment Wizard issues have been fixed:

5.2.5.2. Fixed in Service Pack 3:

The following Package and Deployment Wizard issues have been fixed:

5.2.6. Run-time error with COM DLLs

5.2.6.1. Fixed in Service Pack 3:

The following Microsoft Visual Basic issue has been fixed with Service Pack 1 and is included with this service pack:

5.2.7. Miscellaneous issues

5.2.7.1. Fixed in Service Pack 4:

The following miscellaneous issues have been fixed:

5.2.7.2. Fixed in Service Pack 3:

Microsoft Knowledge Base articles for fixed bugs

Some Microsoft Knowledge Base articles refer to and describe workarounds for bugs that were fixed in Visual Basic Service Pack 4. For a complete list of these articles, see: http://support.microsoft.com/support/vbasic.


5.3. Microsoft Visual C++

This section summarizes the Visual C++ issues fixed with Visual Studio Service Pack 4, arranged according to issue category and service pack, and provides a list of known issues. See the listed Knowledge Base articles for more details.

Service Pack 4 includes all fixes from previous Service Packs, and important fixes from these Service Packs are addressed.

SP4 does not contain the latest Platform SDK headers and libraries. Please go to http://www.microsoft.com/msdownload/platformsdk/setuplauncher.htm to install the latest Plaftorm SDK.

5.3.1. Windows CE ToolKit and Visual C++

Visual Studio Service Pack 4 overwrites certain Visual C++ version 6.0 components that are modified when you install the Microsoft Windows CE Toolkit for Visual C++ 6.0. This means you cannot run the Windows CE Toolkit for Visual C++ 6.0 with Service Pack 4 installed on your machine. The same is true for Service Pack 3; do not use either of these packs if you want to use the Windows CE Toolkit.

Note also that Service Pack 4 does not include an uninstaller. If you install Service Pack 4 and then want to run the Windows CE Toolkit for Visual C++, you must use the Visual C++ 6.0 uninstaller to remove Visual C++ 6.0 and then reinstall both Visual C++ 6.0 and the Windows CE Toolkit for Visual C++. Future versions of the Windows CE Toolkit will address this incompatibility.

5.3.2. Installation considerations

When installing Visual Studio Service Pack 4, it is important that the Service Pack 4 language matches the installed Visual C++ 6.0 language.

Stand-alone Visual C++ 6.0 is only localized into Japanese and German; all other installations will be in English. Therefore, you must install the English version of Service Pack 4 onto any English installation of Visual C++ 6.0.

If Visual C++ 6.0 was installed as part of a localized Visual Studio 6.0, then you should install a matching language version of Service Pack 4. For example, if you installed Spanish, Korean, Italian, French, German, or Japanese versions of Visual Studio 6.0, you should install the same language version of Service Pack 4.

Stand-alone Visual C++ 6.0 installation Service Pack to install
Spanish, Korean, Italian, Simplified Chinese, Taiwanese Chinese, French, English SP4 English
Japanese SP4 Japanese
German SP4 German
Visual Studio–bundled Visual C++6.0 installation Service Pack to install
VS6 Korean SP4 Korean
VS6 Spanish SP4 Spanish
VS6 French SP4 French
VS6 Italian SP4 Italian
VS6 Japanese SP4 Japanese
VS6 German SP4 German

If you have mixed versions of stand-alone installations, such as English Visual C++ 6.0 and Korean Visual Fox Pro 6.0, you will need to install the English version of Service Pack 4 followed by the Korean version of Service Pack 4.

5.3.3. ATL issues

5.3.3.1. Fixed in Service Pack 3:

The following ATL issues have been fixed:

5.3.4. STL issues

5.3.4.1. Fixed in Service Pack 4:

The following STL-related issue has been fixed:

5.3.5. Compiler/Linker/Build issues

5.3.5.1. Fixed in Service Pack 4:

The following build issues have been fixed:

5.3.5.2. Fixed in Service Pack 3:

The following build issues have been fixed:

5.3.6. CRT issues

5.3.6.1. Fixed in Service Pack 4:

The following CRT issue has been fixed:

5.3.6.2. Fixed in Service Pack 3:

The following CRT issue has been fixed:

5.3.6.3. Fixed in Service Pack 2:

MSVCRT.DLL: In Service Pack 2, MSVCRT.DLL was modified to include the Visual C++ 5.0 heap in addition to the Visual C++ 6.0 heap for better compatibility. Visual C++ 6.0 applications will continue to use the Visual C++ 6.0 heap and pre–Visual C++ 6.0 applications will use the Visual C++ 5.0 heap.

The heap-compatibility problems described in the following two Knowledge Base articles have been fixed.

When installing, several of the CRT heap management files are overwritten by updated files that include the code for both the Visual C++ 6.0 heap and the Visual C++ 5.0 heap. If you need to rebuild the Visual C++ 6.0 static libraries, the Visual C++ 5.0 heap code will be included in your static library. It will not be used. The Visual C++ 5.0 heap was added to the Service Pack 2 release to prevent compatibility problems that can arise due to the problems listed earlier. If you do not want the Visual C++ 5.0 code to be included in your rebuilt static library, you should rebuild the library using the original code that was released with Visual C++ 6.0.

5.3.6.4. Fixed in Service Pack 1:

Q193509: In a multithreaded application, one thread calling setlocale while another thread was executing strftime could result in an access violation exception.

5.3.7. Data Access Objects (DAO) issues

5.3.7.1. Fixed in Service Pack 3:

An updated version of DAO 3.6 is included in Visual Studio 6.0 Service Pack 3. DAO 3.6 ships with Office 2000, and the files provided in this service pack make it possible for you to develop for the updated version. DAO 3.6 can be installed along with DAO 3.5x. The SDK source files noted later in this document are not redistributable.

Upgrading to DAO 3.6 is recommended only for existing DAO applications that need access to Office 2000 format databases. For new projects, it is highly recommended you use ActiveX Data Objects (ADO) which is the successor to DAO as the Microsoft preferred data access programming model (built on the new OLE DB technology).

Changes in DAO 3.6

DAO 3.6 files included with Visual Studio Service Pack 3

Included in this service pack are the following files:

To use or build projects with DAO from Visual C++, build the .lib files (see the following instructions). These files can be found on the Visual Studio Service Pack 3 CD in the Support directory or in your destination folder if you downloaded Service Pack 3 from the Microsoft Web site.

DAO SDK headers DAO SDK source
_dbdao.h dbdaouid.cpp
dbdaoerr.h resource.h
dbdaoid.h version.rc
dbdaoint.h stdafx.h
version.usr dbdao.dsp
daogetrw.h Dbdao.dsw
VERSTAMP.H dbdao.mak
VERSION.H dbdao.rc
Dbdao.h Dbdao.cpp

To build the DAO libraries

  1. Copy the DAO SDK Headers and Source files to a directory on a computer running Visual Studio.
  2. In Visual C++, open Dbdao.dsw.
  3. From the Build menu, choose Configurations, and select the type of library you want to use.
  4. From the Build menu, choose Build <dll name>. You can build multiple DLLs at the same time by choosing Batch Build from the Build menu.
  5. Compile your DAO application as usual.

Distributing DAO 3.6

To distribute an application that accesses DAO 3.6 through the DAO SDK classes, install the appropriate DAO36x.DLL for your application.

5.3.8. Debugger issues

5.3.8.1. Fixed in Service Pack 4:

The following debugger issues have been fixed:

5.3.8.2. Fixed in Service Pack 3:

The following debugger issues have been fixed:

5.3.9. IDE issues

5.3.9.1. Fixed in Service Pack 4:

The following Integrated Development Environment (IDE) issues have been fixed:

5.3.9.2. Fixed in Service Pack 3:

The following Integrated Development Environment (IDE) issues have been fixed:

5.3.10. Microsoft Foundation Classes (MFC) issues

5.3.10.1. Fixed in Service Pack 4:

The following MFC issues have been fixed:

5.3.10.2. Fixed in Service Pack 3:

The following MFC issues have been fixed:

5.3.10.3. Fixed in Service Pack 1:

The following MFC issues have been fixed:

5.3.11. Multilanguage issues

5.3.11.1. Fixed in Service Pack 4:

The following multilanguage and language coexistence issue has been fixed:

5.3.11.2. Fixed in Service Pack 3:

The following multilanguage and language coexistence issues have been fixed:

5.3.12. OLE DB Consumer issues

5.3.12.1. Fixed in Service Pack 3:

The following OLE DB Consumer issues have been fixed:

5.3.13. OLE DB Provider issues

5.3.13.1. Fixed in Service Pack 3:

The following OLE DB Provider issues have been fixed:

5.3.14. MDAC issues

5.3.14.1. Fixed in Service Pack 4:

The following Microsoft Data Access Components issue has been fixed:

5.3.15. Visual SourceSafe integration issues

5.3.15.1. Fixed in Service Pack 3:

The following Visual SourceSafe integration issues have been fixed:

5.3.16. Known issues

This section describes current issues for the Visual C++ 6.0 Service Pack 4 release. For issues that have been fixed, see the previous sections.

MDAC Issues

SQL Issues

OLE DB/ODBC Issues

MFC EXE AppWizard fails to show the worksheets in an Excel spreadsheet when specifying an ODBC connection.

When specifying an Excel ODBC connection, the MFC EXE AppWizard shows an empty list and asks the user to select a table. To work around this issue, use an OLE DB Provider for ODBC drivers connection to the Excel spreadsheet instead.

Microsoft OLE DB Provider for SQL Server fails to open a table without a primary key.

The Microsoft OLE DB Provider for SQL Server cannot open a table that does not have a primary key defined. To work around this issue, access the table using the Microsoft OLE DB Provider for ODBC drivers and a SQL server ODBC driver.

Windows 2000 Issues

SDK headers and libraries for Internet Explorer 5 and Windows 2000 not included in Visual Studio Service Pack 4

Visual Studio Service Pack 4 does not include the latest SDK headers and libraries for Internet Explorer 5 or Windows 2000. The updated headers and libraries for Internet Explorer 5 are available from the Microsoft Web & Internet Samples Download Area. For future Windows 2000 SDK updates, see the MSDN SDK web page.

QuickView Command Is Missing from Windows 2000

Version 1.0 of Depends.exe that shipped with Visual C++ 6.0 will fail on Windows 2000 when trying to see a binary image using the External Viewer option

Because Quickview was eliminated from the Windows 2000 operating system, Depends.exe will fail with the following error:

    Dependency Walker External Viewer Error
        Error executing "C:\Winnt\system32\viewers\quickview.exe"
        {Full name of file you're trying to view}

This problem is fixed in Version 2.0, Beta 5 of Depends.exe that shipped with the April 2000 update of the Microsoft Platform SDK for Windows 2000.

MFC Issues

MFC AppWizard generates incorrect column map when using OLE DB ODBC provider and Access

If you generate an MFC database application using OLE DB and you use the OLE DB Provider for ODBC on an Access database, the AppWizard might generate a column map with incorrect ordinals in the Set.h file. The workaround is to reset the ordinals starting at 1. For example:

BEGIN_COLUMN_MAP(CMyTable)
   COLUMN_ENTRY_TYPE(2, DBTYPE_I4, m_id)
   COLUMN_ENTRY_TYPE(3, DBTYPE_STR, m_field1)
   COLUMN_ENTRY_TYPE(4, DBTYPE_STR, m_field2)
END_COLUMN_MAP()

should be:

BEGIN_COLUMN_MAP(CMyTable)
   COLUMN_ENTRY_TYPE(1, DBTYPE_I4, m_id)
   COLUMN_ENTRY_TYPE(2, DBTYPE_STR, m_field1)
   COLUMN_ENTRY_TYPE(3, DBTYPE_STR, m_field2)
END_COLUMN_MAP()

ATL.DLL may use MSStkPrp.dll

ATL applications that include a Control may utilize Stock Properties for Color, Font, or Picture which are supported in MSStkPrp.dll The class ID's for these properties are defined in the ATL header, MSStkPPg.H that resolve to MSStkPrp.dll. Use of these properties by controls is not the default.

MSStkPrp.dll shipped with VC++/VB/VS 6.0. It should be copied to the SYSTEM(32) directory, and registered via the regsvr32.exe utility, or by calling the DllRegisterServer export, directly from your setup program.

The latest English version of MSStkPrp.MSM shipped in Service Pack 4.

Localized versions of MSStkPrp.dll are made available through the VB6 International Package and Deployment Kit (IPDK) that you can download off the web at http://msdn.microsoft.com/vbasic/downloads/ipdk.asp. The Core IPDK download will install the various localized versions of MSSTKPRP.DLL Once you have these files, you need to install the appropriate version for the OS language you are targeting.


5.4. Microsoft Visual FoxPro

5.4.1. Overview of Service Pack 4

Service Pack 4 addresses the following issues:

You can also review changes that were made in Service Pack 3 in the section entitled "Overview of Service Pack 3."

5.4.2. Overview of Service Pack 3

Service Pack 3 contains enhanced language features and bug fixes. For details on language and feature changes included in this update, see VFPSP3.CHM located in the Visual FoxPro 6.0 root directory. VFPSP3.CHM provides the details on the following Visual FoxPro 6 features:

5.4.3. Enhanced and New Language Elements

5.4.3.1. Fixed in Service Pack 4

This update to Visual FoxPro includes the following new features:

When Visual FoxPro writes anything to the screen, it writes first to an off-screen bitmap, and then performs a bit block transfer (bitblt) to the screen. This results in smoother screen painting.

Software that allows remote access to a Visual FoxPro session (for example, Windows Terminal Server) can detect screen changes, mouse moves, and keyboard events. When one of these event occurs, the software broadcasts it over the network. When Visual FoxPro performs a bitblt operation, the entire region is detected as changed, and thus the entire region is sent over the wire to the remote machine.

If you have the line "BITMAP=OFF" in your CONFIG.FPW, then the off-screen bitmaps are not used. However, the performance of Visual FoxPro 6.0 SP4 applications under Windows Terminal Server without off-screen bitmaps is significantly faster, depending on your screen size, net speed, and so on.

Note   It is recommended that you do not use this setting for normal Visual FoxPro applications or COM servers.

There are some side effects that reduce the functionality of certain Visual FoxPro features so that these features are not particularly useful under Windows Terminal Server:

Streaming Output   Streaming output to a form or to _SCREEN is not refreshed. This means that if you "?" something to the screen, and then switch to another window and back again, Visual Foxpro refreshes the screen but does not re-execute the "?" function; as a result, the output is not refreshed.

Form Drawing Methods   The refresh issue applies to Form drawing methods such as FORM.LINE, FORM.PSET, and so on.

Syntax

SYS(2339 [, 0 | 1 ])

0 - CoFreeUnusedLibraries is not called

1 – CoFreeUnusedLibraries is called

Remarks

Syntax

SYS(2800 [, 0 | 32 ])

0 – Disables accessibility aid control tracking (default)

32 – Enables accessibility aid control tracking

Remarks

5.4.3.2. Fixed in Service Pack 3

This update to Visual FoxPro includes the following new and enhanced commands and features:

5.4.4. Bidirectional Issues

5.4.4.1. Fixed in Service Pack 4

5.4.5. Class Browser issues

5.4.5.1. Fixed in Service Pack 3

The following Class Browser issues have been addressed in Service Pack 3:

5.4.6. Component Gallery issues

5.4.6.1. Fixed in Service Pack 3

The following Component Gallery issues have been addressed in Service Pack 3:

5.4.7. FoxPro Foundation Classes issues

5.4.7.1. Fixed in Service Pack 3

The following FoxPro Foundation Classes (FFC) issues have been addressed in Service Pack 3:

5.4.8. Logo Issues

5.4.8.1. Fixed in Service Pack 4

5.4.9. Product issues

5.4.9.1. Fixed in Service Pack 3

Visual FoxPro 6 SP4 provides resolution to the following product issues:

5.4.10. Server Issues

5.4.10.1. Fixed in Service Pack 4

5.4.11. Windows Terminal Server Issues

5.4.11.1. Fixed in Service Pack 4

5.4.12. Wizards Issues

5.4.12.1. Fixed in Service Pack 3

The following Wizards issues have been addressed in Service Pack 3:

Application Wizard

Form Wizard

Label Wizard

Remote View Wizard

Report Wizard

RI Builder

Setup Wizard

SQL Upsizing Wizard

Visual FoxPro Application Framework

Web Publishing Wizard

5.4.13. Xbase Tools Issues

5.4.13.1. Fixed in Service Pack 3

The following Xbase Tools issues have been addressed in Service Pack 3:

Converter

Coverage Profiler

5.4.14. Miscellaneous Issues

5.4.14.1. Fixed in Service Pack 4

The following issues have been addressed in Service Pack 4:

5.4.15. Known Issues

FGETS function update

A minor behavior change was necessary for the FGETS() function related to Knowledge Base article.

Q221747: (C0000005 Fatal Error Passing FGETS() a String >256 chars). The optional nBytes parameter now has a maximum value of 8192. By definition, FGETS() only returns bytes up to a carriage return if one is encountered before the parameter value is reached.

Gridbtns class

A problem exists in the GridBtns class of Wizards\Wizbtns.vcx that prevents data from being saved on certain data input forms. If you drop this class (also referenced in the Component Gallery as Simple Edit Buttons) onto a data input form, edits to records will not be saved. This class is also used by the Form Wizard with the Scrolling Grid style, however, the problem does not exist with these generated forms.

To work around this problem

  1. Replace contents of CheckError method with following:
    #DEFINE ERR_UNIQUEKEY3_LOC "A unique key error violation has occurred. That record will be reverted."
    #DEFINE ERR_RVIEWUPDATE_LOC "A problem occurred updating the remote data. That record will be reverted."
    
    AERROR(aGetErrors)
    
    IF aGetErrors[1] = 1884
       * Uniqueness ID error
       MESSAGEBOX(ERR_UNIQUEKEY3_LOC)
       TABLEREVERT(.T.)
       RETURN
    ENDIF
    
    IF CursorGetProp("sourcetype",.ALIAS)=2
       * If failed to update, check for remote view and revert
       MESSAGEBOX(ERR_RVIEWUPDATE_LOC)
       TABLEREVERT(.T.,.ALIAS)
       RETURN
    ENDIF
  2. Replace the following section of code in the Destroy method:
    IF USED(.ALIAS) AND ATC("CURSOR",.BaseClass)#0 AND ;
       CursorGetProp("sourcetype",.ALIAS)=3 AND ;
       CursorGetProp("buffering",.ALIAS)>1
          TableRevert(.T.,.ALIAS)
          * If your form has General fields, there is a possibility

    with the following:

    IF USED(.ALIAS) AND ATC("CURSOR",.BaseClass)#0 AND ;
       CursorGetProp("buffering",.ALIAS)>1
       IF !TableUpdate(.T.,.T.,.ALIAS) && update on exit
          THIS.CheckError()
       ENDIF
       * If your form has General fields, there is a possibility

Toolbar preferences

After you install Visual Studio Service Pack 3, you must update the system toolbar preferences that are stored in the resource file, Foxuser.DBF. For example, if you have a distributed application that ships a Foxuser file containing a Print Preview toolbar preference that hides the Print button, you need to re-create this preference for the Foxuser file being used by the application.


5.5. Microsoft Visual InterDev

5.5.1. Installation information

Internet Explorer 5

Installing Internet Explorer 5 is strongly advised. Using Internet Explorer 5 with Visual InterDev 6.0 provides enhanced HTML editing and other benefits. Internet Explorer 5 is available from the Microsoft Windows Technologies Internet Explorer Home Page.

"NT SP4 not tested" message

During the Visual InterDev 6.0 installation, if you are installing the NT Option Pack onto Windows NT 4.0 with Service Pack 4, you might see the message "We haven't tested this on NT SP4, do you want to continue?" You should reply "Yes" to this message.

Working with Windows NT 4.0 Service Pack 4

Since Visual InterDev 6.0 was released, Service Pack 4 has become available for Windows NT. It is recommended you install Service Pack 4 on your Windows NT Server computer. Windows NT 4.0 Service Pack 4 is available from the Microsoft Windows Update page.

The availability of Windows NT Service Pack 4 requires slight changes to the installation instructions published in the Visual InterDev 6.0 Readme file (ReadmeVI.HTM). In general:

Corrections to the Visual InterDev 6.0 Readme installation instructions (ReadmeVI.HTM)

Because Windows NT 4.0 Service Pack 4 is now available, the following installation instructions replace the corresponding instructions in the Visual InterDev 6.0 Readme file (ReadmeVI.HTM).

Client installation: If you are installing on Windows NT

The following components are required for the PageNavbar design-time control, remote debugging, and previewing active server pages on your local machine. You may choose not to select these components if you do not want to take advantage of these features.

  1. Select Launch BackOffice Installation Wizard, and click Install.
  2. The BackOffice Installation Wizard will prompt you to select a Custom or Visual InterDev Developer option. Select Custom, and click Next.
  3. Verify the disk space requirements, and click Next.
  4. Select Front Page Server Extensions and MS Data Access Components from the top level of the components list.
  5. Expand the Windows NT Option Pack node, and select:
    Internet Information Server - for NT Server
    Microsoft Management Console
    NT Option Pack Common Files
    Personal Web Server (PWS) - for NT Workstation
    Transaction Server
    Data Access components (for example, Data Access 1.5)
  6. Clear the remaining components. As you clear the other components, the wizard might display a message that warns you of various dependencies. You can choose Yes to ignore the dependencies, because you are using this computer as a client for Visual InterDev and not as a server.
  7. Continue with the remaining steps of the wizard.

Server installation for Windows NT

Perform the following steps if you are installing the server on Windows NT.

  1. When prompted by the wizard, select Launch BackOffice Installation Wizard, and click Install.
  2. The BackOffice Installation Wizard will prompt you to select the Custom or Visual InterDev Developer option. Select the Custom option, and click Next.
  3. Select the following options:
    Windows NT Option Pack 4.0
    MS Data Access Components
    Remote Machine Debugging
    FrontPage Server Extensions
    Visual InterDev Server
  4. Before you click Next, expand the Windows NT Option Pack 4.0 node. In addition to the options selected by default, select the Visual InterDev RAD Remote Deployment Support node. Then expand the Visual InterDev RAD Remote Deployment Support node, and select the second instance of Visual InterDev RAD Remote Deployment Support. Make sure Visual InterDev RAD Remote Deployment Support is selected at both levels.
  5. Click Next, and continue with the remaining steps of the BackOffice Installation Wizard.
  6. Install Windows NT 4.0 Service Pack 4. If you installed Service Pack 4 previously, you should reinstall it to update the server components you installed in Steps 1 through 5.

5.5.2. Changes to Data Connections

Data connections can now be established using OLE DB data source providers, which offers greater flexibility in data sources and more efficient connections. For data sources that do not yet support OLE DB providers, you can continue to use ODBC-based connections.

For more details, see the topic "Connecting to a Database" in the Visual InterDev 6 documentation.

5.5.3. Changes to the HTML Editor

5.5.3.1. Fixed in Service Pack 3:

New glyphs

The glyphs used to mark non-visual elements differ depending on whether the editor is being used with Microsoft Internet Explorer 4.0 or Internet Explorer 5. The glyphs used with Internet Explorer 4 are described in the documentation that accompanies Visual InterDev. The following table lists the glyphs the editor can display if Internet Explorer 5 is installed on the computer.

Glyph Represents
HTML comment (<!— through —>)
Line break (<BR> tag)
Beginning of division (<DIV> tag)
End of division (</DIV> tag)
Beginning of form (<FORM> tag)
End of form (<FORM> tag)
Beginning of paragraph (<P> tag)
End of paragraph (</P> tag)
Beginning of span (<SPAN> tag)
End of span (</SPAN> tag)
Style element (<STYLE>)
Script in the <BODY> portion of the document. This can include client script block (<SCRIPT>) and inline server script block in .asp files (<% %>, or <SCRIPT RUNAT="Server">).
Anchor point for absolutely positioned elements and for image elements that are aligned left or right (for example, <IMG ALIGN=RIGHT>). The glyph appears where the HTML tag defining the element is located in the HTML document.
Unrecognized HTML tags and unmatched ending tags

Improved white space preservation

If you are using Internet Explorer 5, Visual InterDev can do a better job of preserving the exact layout of an HTML file when filtering elements that require special handling, such as scripts and design-time controls (DTCs).

See also Exceptions to white space preservation later in this document.

5.5.4. Debugging ASP script objects

5.5.4.1. Fixed in Service Pack 3:

A new debugging feature has been added to the scripting object model that allows you to catch errors that occur in lower-level components (such as during database access), trace events, and display warnings when script objects encounter possible errors. For more information about debugging and the scripting object model, see the topic "Debugging Script Objects in ASP Pages" in the documentation that accompanies Visual InterDev 6 SP4 and KnowledgeBase article Q224955.

Enabling ASP script object debugging

The documentation for ASP script object debugging incorrectly says that the following script block is automatically added to an .asp page when you first create the page.

<SCRIPT id=DebugDirectives runat=server language=javascript>
// Set these to true to enable debugging or tracing
@set @debug=false
@set @trace=false
</SCRIPT>

This is incorrect. The script block is not added to the page until you enable the scripting object model for that page.

Adding debugging to existing applications

The new script object debugging features are automatically available when you create new webs in Visual InterDev 6. However, they are not automatically added to your existing applications. To take advantage of the debugging features, you must update the script libraries in your applications (projects) and update individual .asp pages, as described in the following procedures.

To update script libraries in an existing application

  1. In Visual InterDev, open the project you want to update.
  2. In the Project Explorer, open the project so you can see the _ScriptLibrary node.
  3. Right-click the _ScriptLibrary node, choose Add, and then choose Add Item.
  4. In the Add Item dialog box, choose the Existing tab. Use the Look in box to navigate to the master script library on your computer, which is usually in the following folder:
    \Program Files\Microsoft Visual Studio\VIntDev98\ScriptLibrary
  5. Select all the files in the folder, and then choose Open.
  6. When prompted, confirm that you want to overwrite the existing files in your project's copy of the script library.
  7. Repeat this procedure for all projects in which you want to use ASP script object debugging.

After updating the script libraries, you can add debugging to individual .asp pages.

To add script object debugging to an individual .asp page

  1. Open the .asp page and add the following block immediately following the <% @Language= %> block at the top of the page:
    <SCRIPT id=DebugDirectives runat=server language=javascript>
    // Set these to true to enable debugging or tracing
    @set @debug=false
    @set @trace=false
    </SCRIPT>
  2. Set the debugging options you want. For details, see the topic "Debugging Script Objects in ASP Pages" in the documentation.

5.5.5. Localized error messages for the Script Library

5.5.5.1. Fixed in Service Pack 3:

If an error occurs inside the script library when you are using Visual InterDev design-time controls, the resulting error message is displayed in English, along with an error number. You may look up the translated error text by error number. Translated versions of these error messages are available in SLErrors.htm on the Service Pack 3 CD under the appropriate language subdirectory in the \support folder. If you downloaded the service pack, SLErrors.htm is located in the folder in which you extracted the files.

5.5.6. Other fixes

5.5.6.1. Fixed in Service Pack 4:

The following problems have also been fixed in Visual Studio 6.0 Service Pack 4. The "Q" number that precedes most fixes indicates the ID of a Knowledge Base article that provides further details about the problem and the fix.

5.5.6.2. Fixed in Service Pack 3:

The following problems have also been fixed in Visual Studio 6.0 Service Pack 3. The "Q" number that precedes most fixes indicates the ID of a Knowledge Base article that provides further details about the problem and the fix.

5.5.7. Known issues

Exceptions to white space preservation in HTML editor

When you load a document into the HTML editor or switch between Design view and Source view, the editor attempts to preserve the format of the document as closely as possible. However, this is not always possible. If you are using Internet Explorer 5, the following changes might be made to the document:

Individual themes deleted during recalculation

When using source control to obtain files that belong to a theme, always perform a Check Out or Get Local on all files in the theme. You can do this by selecting a theme folder before getting the files. Otherwise, if part of a theme is local and the remainder is on the server, you might encounter problems. Recalculating links or switching from local to master mode might cause the theme to be deleted from your project. Likewise, check all files back in at the same time.

RDS objects on page cause "failed to load" message

If a page contains an <OBJECT> tag that references an RDS component, when you switch to Source view in the HTML editor, you will see the message:

Some objects have failed to load. The objects will be displayed as text. 

This occurs because the RDS objects do not have a visual representation, so Source view cannot render them. However, the objects will function correctly.

Installing VBScript or JScript version 5.1.x disables Intellisense

After upgrading to version 5.1.x of VBScript or JScript, the Intellisense feature of the code editor may fail to display the members of an object. On NT4 you may experience a long delay before the member list appears; on Windows 2000 the list may not appear at all.

This only occurs when you use a fully qualified object (i.e. document.Form1.Select1). If you remove the document portion of the reference (i.e. Form1.Select1), Intellisense will display the member list properly.


5.6. Microsoft Visual J++

5.6.1. Virtual Machine and Windows 2000

The Microsoft Virtual Machine will currently not install on Windows 2000, due to File System Protection. This means that the fixes introduced in Service Pack 4 will not apply to these systems.

This problem is due to be resolved with the release of Service Pack 1 for Windows 2000.

5.6.2. Installation information

Some features of Visual J++ 6.0 relating to debugging Microsoft Transaction Server (MTS) require Windows NT 4.0 Service Pack 6a (SP6a). Windows NT 4.0 SP6a is available from the Microsoft Windows Update page.

5.6.3. New Microsoft Virtual Machine

In response to the automation issues noted in Automation, the Microsoft® virtual machine files have been updated, beginning with Service Pack 2. The Microsoft virtual machine version included in this service pack is listed in the Visual J++ section of the file list below. This change will be applied both on the machine where Microsoft Visual J++ is installed and also to the Visual J++ redistributable folder, so Visual J++ applications that are distributed will also include the updated Automation files.

To switch between retail and debug versions of the Microsoft virtual machine system classes, run classd.exe or classr.exe.

This service pack contains the required Visual J++ files needed to comply with the preliminary ruling issued by Federal District Court Judge Ronald H. Whyte. These changes were also included in Service Pack 2. For more information, please read \vj98\extwarn.txt in your Visual Studio folder or go to http://msdn.microsoft.com/visualj.

5.6.4. Compiler, Debugger, ActiveX, and IDE fixes

5.6.4.1. Fixed in Service Pack 4:

5.6.4.2. Fixed in Service Pack 3:

In this service pack release, the following issues in the general programming environment have been resolved:

5.6.5. Microsoft Windows Foundation Classes fixes

5.6.5.1. Fixed in Service Pack 3:

ActiveX support fixes

Code-behind-HTML fixes

Other WFC library and control fixes

5.6.6. Other fixes

5.6.6.1. Fixed in Service Pack 3:


5.7. Microsoft Visual SourceSafe

Visual Studio Service Pack 4 includes Visual SourceSafe version 6.0a. Version 6.0a contains fixes to Visual SourceSafe 6.0 issues, but there are no new features. Visual SourceSafe customers will be upgraded to version 6.0a after installing Visual Studio 6.0 Service Pack 4.

5.7.1.1. Fixed in Service Pack 4

The following Visual SourceSafe issues have been fixed in this service pack:

5.7.1.2. Fixed in Service Pack 3

The following Visual SourceSafe issues have been fixed in this service pack:

5.8. Microsoft Visual Studio Analyzer

5.8.1.1. Fixed in Service Pack 4

What is the COM+ 1.0 Event Bridge?

COM+ 1.0 replaces MTS 2.0. MTS 2.0 supported Visual Studio Analyzer. However, this is not the case for COM+ 1.0. COM+1.0 generates events that are similar to Visual Studio Analyzer events, but they are not compatible with Visual Studio Analyzer. The bridge fixes this problem by subscribing to these events and converting them to Visual Studio Analyzer events.

Who should install the COM+ 1.0 Event Bridge?

You should install the COM+ 1.0 Event Bridge if you are using Visual Studio Analyzer 6.0 with MTS 2.0 and analyzing MTS components, and you have upgraded to COM+1.0 by installing Windows 2000. When you upgrade to COM+ 1.0, you can no longer get MTS events with Visual Studio Analyzer. After you install the COM+ Event Bridge, you can again analyze MTS components.

Installing the COM+ 1.0 Event Bridge

To install the bridge, you register the Vamts.dll as follows:

  1. At the command prompt, type:

    regsvr32 vamts.dll

  2. Add the user VUSR_localcomputer to the Administrators group. The bridge runs as this user. Localcomputer is the name of the computer on which you are installing the bridge.

    Because of an issue with COM+ event subscription, the bridge must run as an administrator in order to subscribe to COM+ events. Microsoft is investigating this issue.

To remove the bridge, unregister the Vamts.dll as follows:

  1. At the command prompt, type:

    regsvr32 /u vamts.dll

  2. Remove VUSR_localcomputer from the Administrators group.

Using Visual Studio Analyzer to Collect COM+ 1.0 Events

After you install the COM+ Event Bridge, it becomes a registered Visual Studio Analyzer component with the name COM+ Event Source. Some of the original events generated by the MTS Event Source are also generated by the COM+ Event Source. Because there is new functionality in COM+ 1.0, there are also new events being generated. These new event names are prefixed with COM+, for example, COM+ User Exception.

Fixing Existing Visual Studio Analyzer 6.0 Projects

You must modify filters that specify the MTS Event Source directly so that they reference the COM+ Event Source. Filters that specify All Components need no modification.

Additional Information

For more information on Visual Studio Analyzer version 6.0, see MSDN Online at http://msdn.microsoft.com/library/.