Microsoft Visual Studio 6.0 Service Pack 3 Readme

© 1999 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 3 Readme contains the following sections:

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

For the latest year 2000 information regarding Microsoft products, see the Microsoft Year 2000 Readiness Disclosure and Resource Center Web Site located at http://microsoft.com/year2000. You can also call 1-888-MSFT-Y2K within the United States, toll-free, or contact your local Microsoft subsidiary.

Overview

The Microsoft Visual Studio 6.0 Service Pack 3 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 3 includes all of the fixes in Service Packs 1 and 2 and updates the following Visual Studio applications:

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

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 SetupSP3.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\SetupSP3.exe (Simplified Chinese)
\cht\SetupSP3.exe (Traditional Chinese)
\deu\SetupSP3.exe (German)
\enu\SetupSP3.exe (English)
\esp\SetupSP3.exe (Spanish)
\fra\SetupSP3.exe (French)
\ita\SetupSP3.exe (Italian)
\jpn\SetupSP3.exe (Japanese)
\kor\SetupSP3.exe (Korean)

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

Note   The service pack files for English, French, German, Italian, and Spanish are on one CD-ROM. The files for English, Simplified Chinese, Traditional Chinese, Japanese, and Korean are on another CD-ROM.

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.

Installing Service Pack 3 on Windows 2000

Installing Service Pack 3 on Windows 2000 Beta 3 RC1

Run-time dynamic-link libraries (DLLs) and several other files are not updated on Windows 2000 Beta 3 RC1 because of the System File Protection feature in Windows 2000. Microsoft does not support installing Service Pack 3 on Windows 2000 Beta 3 RC1 but does support installation on the final release of Windows 2000 Beta 3.

To see the fixes that will not be available if you install the Visual Studio 6.0 SP3 on Windows 2000 Beta 3 RC1, see Microsoft Foundation Classes (MFC) issues and ATL issues.

Installing Service Pack 3 on Windows 2000 Beta 3

During setup of Visual Studio SP3 on Windows 2000 Beta 3, Windows 2000 will return this error message:

"File replacement was attempted on the protected system file <file>. This file needs to be restored to the correct Microsoft version to maintain system stability."

This error message will appear for several files. The files listed in the error messages will not be installed by Service Pack 3.

For the file expsrv.dll, this error is not critical. The update to expsrv.dll corrected a minor issue where an erroneous message from the Visual Basic Product Deployment Wizard would occur. This error can be safely ignored by Visual Basic users as well as by users of other Visual Studio products.

The other files, such as msdbg.dll, mdm.exe and pdm.dll contain important fixes that are necessary to Visual Studio, especially when developing applications against Microsoft® Internet Information Server (IIS). Because these are system files, Windows 2000 will not allow them to be updated, and the System File Protection error message will occur when running the Visual Studio SP3 Setup.

A QFE for Windows 2000 Beta 3 will be provided separately to obtain these newer files for that platform. For instructions on how to obtain this update, see the Microsoft Visual Studio Home Page. This problem is specific to Windows 2000 Beta 3, and not the retail version of Windows 2000.

Debugging Visual C++ and Visual J++ applications on Windows 2000 Beta 3

A late-breaking issue may prevent the debugging of Visual C++ and Visual J++ applications on Windows 2000 Beta 3. You can compile your applications. To restore debugging functionality, see the Microsoft Visual Studio Web site.

Visual Studio 6.0 Service Pack 3 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 3. Click one of the following product names to view its specific installation requirements.

Installing Microsoft Data Access Components 2.1

Microsoft Data Access Components (MDAC) 2.1 Service Pack 1 or later is required for Visual Studio 6.0 Service Pack 3. MDAC 2.1 SP1 is included with Visual Studio 6.0 Service Pack 3. If you do not have MDAC 2.1 SP1 or later installed, you must install it before installing the service pack. The Service Pack Setup will inform you if you must install MDAC 2.1 SP1.

Because MDAC 2.1 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.1 SP1 for your system's language setting.

For important information about a known issue with MDAC 2.1, see Record deletion causes loss of cursor position with ADO or Microsoft Access ODBC driver.

To install MDAC 2.1 SP1

If MDAC 2.1 Setup requests that you restart your computer, you must do so and then restart Visual Studio Service Pack 3 Setup (SetupSP3.exe).

Installing the MDAC 2.1 library and header files

Setup does not install the MDAC 2.1 library and header files. Visual Studio Service Pack 3 has been tested with the MDAC 2.0 headers and libraries against the MDAC 2.1 binaries. If you must use specific MDAC 2.1 interfaces, you must install the headers and libraries manually. To do so, copy them into the VC98\include and VC98\lib directories respectively. The headers and libraries are in the \Support folder on the Service Pack CD or in your extraction folder if you downloaded the service pack from the Internet, and consist of the following files:

Adc.h adoctint.h adodef.h adoid.h
Adoint.h adojet.h adojet.idl adomd.h
Adomd.idl cmdtree.h icrsint.h jetoledb.h
Jetoledb.idl jetoledb.lib msado15.h msado15.idl
Msdadc.h msdaguid.h msdaora.h msdaosp.h
Msdasc.h msdasc.lib msdasql.h msdatsrc.h
Msdatsrc.tlb msdshape.h msjetoledb.h msremote.h
Odbc32.lib odbccp32.lib odbcinst.h oledb.h
Oledb.lib oledbdep.h oledberr.h osptk.lib
Persist.h simpdata.h simpdata.tlb sql.h
Sqlext.h sqloledb.h sqltypes.h sqlucode.h

Note   The file msjetoledb.h is named "msjetodb.h" on the CD and in the Internet download. If you copy this file from the CD or your download extraction folder, you must rename it from "msjetodb.h" to "msjetoledb.h."

You won't need to rebuild the MFC DLLs when you install the MDAC 2.1 headers and libraries. However, if you do rebuild the DLLs, you must copy the MFC header file ocdb.h into the mfc\src directory before recompiling.

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 SetupSP3.exe for each product's language to install Service Pack 3.

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 3, 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.

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.

Uninstalling the Visual Studio 6.0 Service Pack

The Service Pack cannot be uninstalled independently of Visual Studio.

Known issues

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 3 Setup (SetupSP3.exe) again.

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 3 CD-ROM in the drive. You can then successfully install Internet Explorer 5.

Notes on Fixes

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

Microsoft Visual Studio

Automation fix

The following run-time issue has been fixed with Service Pack 3 and was also fixed with Service Pack 1:

Data Tools update

The following Year 2000 issue has been addressed and updated in Visual Studio Service Pack 3.

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 http://www.microsoft.com/windows/euro.asp. 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:

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.

Microsoft ActiveX Data Objects (ADO) documentation

The Microsoft® ActiveX® Data Objects documentation has been updated. See the ADO section under Visual Basic 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:

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.

Miscellaneous fixes

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.

Known issues

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. Complete details about this issue can be obtained from Knowledge Base article Q230131. 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.

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.

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 3, 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.

Controls issues

The following Controls issues have been fixed:

International product issues

The following international product issues have been fixed:

Microsoft ActiveX Data Objects (ADO) documentation

Updated Microsoft ActiveX Data Objects (ADO) documentation is installed with Visual Studio 6 Service Pack 3. 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.

For important information about a known issue with ADO, see Record deletion causes loss of cursor position with ADO or Microsoft Access ODBC driver.

Package and Deployment Wizard issues

The following Package and Deployment Wizard issues have been fixed:

Run-time error with COM DLLs

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

If your applications download run-time components from the Web on setup, note that the following files have changed with this Service Pack:

msvbvm60.cab
vbrun60.cab
oleaut.cab

Miscellaneous issues

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 3. For a complete list of these articles, see: http://support.microsoft.com/support/vbasic.

Microsoft Visual C++

The following is a summary of Visual C++ issues fixed with Service Pack 3, arranged according to issue category and service pack, and a list of known issues. See the listed Knowledge Base articles for more details.

Windows CE ToolKit and Visual Studio 6.0 Service Pack 3

Visual Studio Service Pack 3 overwrites certain Visual C++ 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 3 installed on your machine. Note also that Service Pack 3 does not include an uninstaller. If you install Service Pack 3 and then want to run the Windows CE Toolkit for Visual C++, you must remove Visual C++ 6.0 using the Visual C++ 6.0 uninstaller and then reinstall Visual C++ 6.0 and the Windows CE Toolkit for Visual C++. Future versions of the Windows CE Toolkit for Visual C++ will address this incompatibility with Visual Studio 6.0 Service Pack 3.

ATL issues

Installing Service Pack 3 on Windows 2000 Beta 3

For information about installing Visual Studio 6.0 Service Pack 3 on Windows 2000 Beta 3, see Installing Service Pack 3 on Windows 2000.

ATL fixes

The following ATL issues have been fixed:

Compiler/Linker/Build issues

The following build issues have been fixed:

CRT issues

The following CRT issue has been fixed in Service Pack 3.

The following CRT issues have been fixed in previous service packs and are included in Service Pack 3.

Service Pack 1
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 SP2 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.

Updated Data Access Objects (DAO)

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 extraction folder if you downloaded the service pack from the Internet.

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.

Debugger issues

The following debugger issues have been fixed:

IDE issues

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

Microsoft Foundation Classes (MFC) issues

Installing Service Pack 3 on Windows 2000 Beta 3

For information about installing Visual Studio 6.0 Service Pack 3 on Windows 2000 Beta 3, see Installing Service Pack 3 on Windows 2000.

Using Access 2000 databases with MFC 6.0.

MFC 6.0 has the ability to use Microsoft® Access 2000 databases. To engage this support in your application, you must enable DAO 3.6 by:

MFC fixes

The following MFC issues have been fixed:

Service Pack 1

The following MFC issues were fixed in Service Pack 1 and are included in Service Pack 3:

Multilanguage issues

The following multilanguage and language coexistence issues have been fixed:

OLE DB Consumer issues

The following OLE DB Consumer issues have been fixed:

OLE DB Provider issues

The following OLE DB Provider issues have been fixed:

Visual SourceSafe integration issues

The following Visual SourceSafe integration issues have been fixed:

Known issues

This section describes current issues for the Visual C++ 6.0 SP3 release. For issues that have been fixed, see the sections preceding this one.

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.

MFC EXE Appwizard generated application fails to open recordset on an Access table through the OLE DB provider for ODBC drivers.

When an MFC EXE Appwizard-generated application that connects to an Access table through the OLE DB provider for ODBC drivers is executed, it displays a "Recordset failed to open" message. There is no current workaround for this problem. It will be fixed in a future release of the Microsoft Data Access Components (MDAC).

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.

Record deletion causes loss of cursor position with ADO or Microsoft Access ODBC driver

For important information about a known issue with the MDAC 2.1 ODBC driver, see Record deletion causes loss of cursor position with ADO or Microsoft Access ODBC driver.

Using MDAC 2.1 with Visual Studio SP3

Setup does not install the MDAC 2.1 library and header files. Visual Studio Service Pack 3 has been tested with the MDAC 2.0 headers and libraries against the MDAC 2.1 binaries. If you need to use specific MDAC 2.1 interfaces, you will need to install the headers and libraries manually. For information on installing the library and header files, see Installing Microsoft Data Access Components 2.1.

Windows 2000 issues

Debugger may crash on Windows 2000 Beta 3

A late-breaking issue may prevent the debugging of Visual C++ applications on Windows 2000 Beta 3. You can compile your applications. To restore debugging functionality, see the Microsoft Visual Studio Web site.

Debugger may not report exceptions correctly on Windows 2000

On some releases of Windows 2000, the debugger will not report certain types of exceptions correctly. For example, sometimes the debugger will let the exception pass through to the CRT, where an abort message will be reported. This Windows 2000 issue is expected to be fixed in a future release.

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

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

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 ODBC provider 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()

Microsoft Visual FoxPro

Overview

This service pack 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:

Enhanced and new language elements

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

Class Browser issues

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

Component Gallery issues

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

FoxPro Foundation Classes issues

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

Product issues

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

Wizards issues

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

Xbase Tools issues

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

Converter
Coverage Profiler

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() will only return 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 which 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 installing Visual Studio Service Pack 3, you must update the system toolbar preferences 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.

Microsoft Visual InterDev

Installation information

Connecting to a SQL Server

If you will be using MDAC 2.1 to connect to a SQL Server, you must run the version of instcat.sql installed with MDAC 2.1 SP1 which can be found in your system directory.

To run instcat.sql:

  1. From the Start button, choose Programs, Microsoft SQL Server, and then run ISQL_w.
  2. When prompted, connect to the SQL Server server that you want to update.
  3. From the File menu, choose Open. From your system directory, select instcat.sql.
  4. From the Query menu, choose Execute.
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 provided on the Visual Studio 6.0 Service Pack 3 CD in the IE5 folder under your language folder. It is also 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.

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 SP3 documentation.

Changes to the HTML Editor

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.

Debugging ASP script objects

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 SP3 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.

Localized error messages for the Script Library

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.

Other fixes

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.

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.

Microsoft Visual J++

Installation information

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

Visual J++ applications cannot be debugged on Windows 2000 Beta 3

A late-breaking issue may prevent the debugging of Visual J++ applications on Windows 2000 Beta 3. You can compile your applications. To restore debugging functionality, see the Microsoft Visual Studio Web site.

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.

Compiler, Debugger, ActiveX, and IDE fixes

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

Microsoft Windows Foundation Classes fixes

The following items have been fixed in the 1.0.0.8443 release of the Windows Foundation Classes. This release is installed with the Microsoft virtual machine included with Service Pack 3.

ActiveX support fixes
Code-behind-HTML fixes

See also Known issues.

Other WFC library and control fixes

Other fixes

Known issues

Access 2000 databases must be connected via ODBC in Data Form Wizard

You might get a "Unrecognized database format" error when connecting to an Access 2000 database using the Data Form Wizard. To connect to an Access 2000 database, specify the database type as ODBC (rather than Access, which will assume Access 98) on the "Database Type" page. On the Connect Information page, you can then specify the Access 2000 database file (*.mdb) as the database, and Microsoft Access Driver (*.mdb) as the driver. Alternatively, you could set up a DSN using the ODBC Data Source wizard from the Windows Control Panel and specify the DSN on the Connect Information page of the Data Form Wizard.

Code-behind HTML support and Windows 2000 Beta 3

WFC controls from the com.ms.wfc.ui package that are added to a DhDocument (via the DhComponentWrapper() method) do not work on Windows 2000 Beta 3. This issue will be fixed in a future release of Windows 2000.

Microsoft Visual SourceSafe

The following Visual SourceSafe issues have been fixed in Service Pack 3:

Finding More Information

For more in-depth 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.

File Versions

The following table lists the developer tools that have been updated in this Visual Studio 6.0 Service Pack. It also lists the key files you should check to ascertain version information.


Product
Files		 Version on Release Version in SP3
Data Tools mdt2db.dll 2.0.0.8171 2.0.0.8425
  mdt2dbns.dll 2.0.0.8171 2.0.0.8425
  mdt2dbui.dll 2.0.0.8171 2.0.0.8425
  mdt2dd.dll 2.0.0.8171 2.0.0.8425
  mdt2ddui.dll 2.0.0.8171 2.0.0.8425
  mdt2df.dll 2.0.0.8171 2.0.0.8425
  mdt2dfx.dll 2.0.0.8171 2.0.0.8425
  mdt2fref.dll 2.0.0.8171 2.0.0.8425
  mdt2fw.dll 2.0.0.8171 2.0.0.8425
  mdt2fw95.dll 2.0.0.8171 2.0.0.8425
  mdt2fwui.dll 2.0.0.8171 2.0.0.8456
  mdt2g.dll 2.0.0.8171 2.0.0.8425
  mdt2gddo.dll 2.0.0.8171 2.0.0.8425
  mdt2gddr.dll 2.0.0.8171 2.0.0.8425
  mdt2lv.dll 2.0.0.8171 2.0.0.8425
  mdt2lvui.dll 2.0.0.8171 2.0.0.8425
  mdt2qd.dll 2.0.0.8171 2.0.0.8456
  mdt2qdui.dll 2.0.0.8171 2.0.0.8425
  mdt2sd.dll 2.0.0.8171 2.0.0.8425
  mdt2sdui.dll 2.0.0.8171 2.0.0.8425
Environment msenv.dll 6.1.81.71 6.1.84.26
HTML Help 1.21 hh.exe 4.72.8171.0 4.73.8412.0
  hhctrl.ocx 4.72.8164.0 4.73.8412.0
  htmlhelp.exe 4.71.1015.0 4.71.1015.0
  itircl.dll 4.72.7276.0 4.72.7276.0
  itss.dll 4.72.8037.0 4.72.8084.0
Internet Explorer 5.0      
DAO/Jet _dbdao.h    
  dao360.dll   3.60.2521.8
  daogetrw.h    
  dbdao.cpp    
  dbdao.dsp    
  dbdao.dsw    
  dbdao.h    
  dbdao.mak    
  dbdao.rc    
  dbdaoerr.h    
  dbdaoid.h    
  dbdaoint.h    
  dbdaouid.cpp    
  msjet35.dll 3.51.623.4 3.51.2723.0
  msjt4jlt.dll 3.52.1527.3 3.52.2723.0
  msrepl35.dll 3.51.623.0 3.51.2404.0
  msscript.ocx 1.0.0.2604 1.0.0.3715
  odbcstf.dll 3.510.3002.13 3.510.3904.0
  resource.h    
  stdafx.h    
  version.h    
  version.rc    
  version.usr    
  verstamp.h    
MS Data Access Components 2.1 SP1 adc.h    
  adoctint.h    
  adoid.h    
  adoint.h    
  adojet.h    
  adojet.idl    
  adomd.h    
  adomd.idl    
  cmdtree.h    
  icrsint.h    
  jetoledb.h    
  jetoledb.idl    
  jetoledb.lib    
  mdac_typ.cab    
  mdac_typ.exe 4.71.1015.0 21.1.3711.11
  msado15.h    
  msado15.idl    
  msdadc.h    
  msdaguid.h    
  msdaora.h    
  msdaosp.h    
  msdasc.h    
  msdasc.lib    
  msdasql.h    
  msdatsrc.h    
  msdatsrc.tlb    
  msdshape.h    
  msjetoledb.h    
  msremote.h    
  ocdb.h    
  odbc32.lib    
  odbccp32.lib    
  odbcinst.h    
  oledb.h    
  oledb.lib    
  oledbdep.h    
  oledberr.h    
  osptk.lib    
  persist.h    
  simpdata.h    
  simpdata.tlb    
  sql.h    
  sqlext.h    
  sqloledb.h    
  sqltypes.h    
  sqlucode.h    
OLE Automation asycfilt.dll 2.30.4261.1 2.40.4275.1
  oleaut32.dll 2.30.4261.1 2.40.4275.1
  olepro32.dll 5.0.4261.1 5.0.4275.1
  stdole2.tlb 2.30.4261.1 2.40.4275.1
Scripting 5.0 dispex.dll 4.0.0.2926 5.0.0.3715
  jschs.dll   5.0.0.3715
  jscht.dll   5.0.0.3715
  jscript.dll 4.0.0.2920 5.0.0.3715
  jsde.dll   5.0.0.3715
  jses.dll   5.0.0.3715
  jsfr.dll   5.0.0.3715
  jsit.dll   5.0.0.3715
  jsjp.dll   5.0.0.3715
  jsko.dll   5.0.0.3715
  scochs.dll   1.0.0.3715
  scocht.dll   1.0.0.3715
  scode.dll   1.0.0.3715
  scoes.dll   1.0.0.3715
  scofr.dll   1.0.0.3715
  scoit.dll   1.0.0.3715
  scojp.dll   1.0.0.3715
  scoko.dll   1.0.0.3715
  scrobj.dll   1.0.0.3715
  scrrnchs.dll   5.0.0.3715
  scrrncht.dll   5.0.0.3715
  scrrnde.dll   5.0.0.3715
  scrrnes.dll   5.0.0.3715
  scrrnfr.dll   5.0.0.3715
  scrrnit.dll   5.0.0.3715
  scrrnjp.dll   5.0.0.3715
  scrrnko.dll   5.0.0.3715
  scrrun.dll 4.0.0.2926 5.0.0.3715
  vbschs.dll   5.0.0.3715
  vbscht.dll   5.0.0.3715
  vbscript.dll 4.0.0.2926 5.0.0.3715
  vbsde.dll   5.0.0.3715
  vbses.dll   5.0.0.3715
  vbsfr.dll   5.0.0.3715
  vbsit.dll   5.0.0.3715
  vbsjp.dll   5.0.0.3715
  vbsko.dll   5.0.0.3715
Visual Basic ado210.chm    
  appwiz.ocx 6.0.0.8177 6.0.0.8450
  begin.frm    
  begin.frx    
  c2.dll 12.0.8168.0 12.0.8447.0
  co2c40en.dll 4.6.1.106 4.6.1.106
  comct332.cab    
  comct332.dep    
  comct332.ocx 6.0.0.8169 6.0.0.8450
  comct3ax.cab    
  comdlg32.cab    
  comdlg32.dep    
  comdlg32.ocx 5.1.43.19 6.0.84.18
  comdlgax.cab    
  common.bas    
  commonrc.h    
  commonrc.rc    
  copy.frm    
  copy.frx    
  datarpt.dsr    
  dataview.dll 6.0.0.8169 6.0.0.8450
  dlgobjs.dll 4.0.1.23 4.0.1.23
  dskspace.frm    
  dskspace.frx    
  expsrv.dll 6.0.0.8167 6.0.0.8269
  group.frm    
  group.frx    
  hostwiz.dll 6.0.0.8169 6.0.0.8450
  htmpdfr.dll   6.0.81.63
  htmprfr.dll   6.0.81.63
  htmutil.dll 6.0.0.8152 6.0.0.8405
  install.bmp    
  logging.bas    
  makecab.exe   1.0.603.4
  mci32.cab    
  mci32.dep    
  mci32.ocx 6.0.81.69 6.0.84.18
  mci32ax.cab    
  message.frm    
  message.frx    
  modshell.bas    
  msaddcax.cab    
  msadodc.cab    
  msadodc.dep    
  msadodc.ocx 6.0.81.71 6.0.84.18
  msbind.cab    
  msbind.dep    
  msbind.dll 6.0.81.69 6.0.84.50
  msbindax.cab    
  mscdrun.cab    
  mschrt20.cab    
  mschrt20.dep    
  mschrt20.ocx 6.0.81.77 6.0.84.18
  mschrtax.cab    
  mscmc2ax.cab    
  mscmctax.cab    
  mscomct2.cab    
  mscomct2.dep    
  mscomct2.ocx 6.0.81.77 6.0.84.18
  mscomctl.cab    
  mscomctl.dep    
  mscomctl.ocx 6.0.81.77 6.0.84.98
  msdagdax.cab    
  msdalsax.cab    
  msdatgrd.cab    
  msdatgrd.dep    
  msdatgrd.ocx 6.0.81.69 6.0.84.18
  msdatlst.cab    
  msdatlst.dep    
  msdatlst.ocx 6.0.81.69 6.0.84.18
  msde.dll 6.0.0.3005 6.0.84.50
  msderun.cab    
  msderun.dep    
  msderun.dll 6.0.0.3005 6.0.84.50
  msdeui.dll 6.0.0.3005 6.0.0.3005
  msflxgax.cab    
  msflxgrd.cab    
  msflxgrd.dep    
  msflxgrd.ocx 5.1.43.19 6.0.84.18
  mshfgax.cab    
  mshflxgd.cab    
  mshflxgd.dep    
  mshflxgd.ocx 6.0.30.5 6.0.84.18
  msmask32.cab    
  msmask32.dep    
  msmask32.ocx 6.0.81.69 6.0.84.18
  msmaskax.cab    
  msprpcht.cab    
  msprpcht.dll   6.0.84.50
  msrdc20.cab    
  msrdc20.dep    
  msrdc20.ocx 6.0.81.69 6.0.84.18
  msrdc2ax.cab    
  msrdo20.cab    
  msrdo20.dep    
  msrdo20.dll 6.0.81.69 6.0.84.50
  msstdfmt.dep    
  msstdfmt.dll 6.0.81.69 6.0.84.50
  msvbv6ax.cab    
  msvbvm60.cab    
  msvbvm60.dll 6.0.81.76 6.0.84.95
  mswcrun.cab    
  mswcrun.dep    
  mswcrun.dll 6.0.81.69 6.0.84.50
  mswless.dep    
  mswless.ocx 6.0.81.69 6.0.84.50
  odbc log in.frm    
  oleaut.cab    
  oleautax.cab    
  overwrit.frm    
  overwrit.frx    
  path.frm    
  path.frx    
  pdaddin.dll 6.0.0.8169 6.0.0.8450
  pdcmdln.exe 6.0.0.8169 6.0.0.8450
  pdwizard.ocx 6.0.0.8169 6.0.0.8450
  pdwizchs.dll   6.0.0.8450
  pdwizcht.dll   6.0.0.8450
  pdwizdeu.dll   6.0.0.8450
  pdwizesn.dll   6.0.0.8450
  pdwizfra.dll   6.0.0.8450
  pdwizita.dll   6.0.0.8450
  pdwizjpn.dll   6.0.0.8450
  pdwizkor.dll   6.0.0.8450
  picclp32.cab    
  picclp32.dep    
  picclp32.ocx 6.0.81.69 6.0.84.18
  picclpax.cab    
  rdocurs.dll 5.0.81.69 6.0.84.50
  registry.bas    
  repvbrc.dll 6.0.8161.0 6.0.8161.1
  resedit.dll 6.0.0.8169 6.0.0.8450
  richtx32.cab    
  richtx32.dep    
  richtx32.ocx 6.0.81.69 6.0.84.18
  richtxax.cab    
  serverdt.frm    
  serverdt.frx    
  setup.exe 2.20.903.0 6.0.84.50
  setup1.bas    
  setup1.exe 6.0.0.8171 6.0.0.8450
  setup1.frm    
  setup1.frx    
  setup1.ico    
  setup1.rc    
  setup1.res    
  setup1.vbp    
  setupres.bas    
  setupres.h    
  sqlparse.dll 5.0.81.69 5.0.84.61
  st6unst.exe 6.0.81.69 6.0.84.50
  tabctl32.cab    
  tabctl32.dep    
  tabctl32.ocx 5.1.43.19 6.0.84.18
  tabctlax.cab    
  vb6.exe 6.0.81.76 6.0.84.64
  vb6debug.dll 6.0.81.69 6.0.84.62
  vb6dep.ini    
  vb6ide.dll 5.0.81.69 6.0.84.50
  vb6stkit.dll 6.0.81.69 6.0.84.50
  vba6.dll 6.0.0.8169 6.0.0.8495
  vbreadme.htm    
  vbrun60.cab    
  vbrun6ax.cab    
  vbsdidb.dll 5.0.81.70 5.0.84.61
  vbshell.odl    
  vbshell.tlb    
  wbclsdsr.ocx 6.0.81.69 6.0.84.50
  welcome.frm    
  welcome.frx    
Visual C++ afxbld_.h    
  afxisapi.h    
  afxodlgs.h    
  afxwin1.inl    
  appui1.cpp    
  arccore.cpp    
  atl.dll 3.0.8168.0 3.0.8449.0
  atl.lib    
  atlbase.h    
  atlcom.h    
  atldb.h    
  atldbcli.h    
  atlimpl.cpp    
  barcore.cpp    
  c1.dll 12.0.8168.0 12.0.8472.0
  c1xx.dll 12.0.8168.0 12.0.8472.0
  c2.dll 12.0.8168.0 12.0.8447.0
  calloc.c    
  ctlinplc.cpp    
  cvtres.exe 5.0.1720.1 5.0.1736.1
  daocore.cpp    
  dbgheap.c    
  delete.cpp    
  devaut1.pkg 6.0.8168.0 6.0.8447.0
  devbld.pkg 6.0.8168.0 6.0.8447.0
  devclvw.pkg 6.0.8168.0 6.0.8447.0
  devcpp.pkg 6.0.8168.0 6.0.8447.0
  devedit.pkg 6.0.8168.0 6.0.8447.0
  devprj.pkg 6.0.8168.0 6.0.8447.0
  devshl.dll 6.0.8168.0 6.0.8472.0
  dlgcore.cpp    
  dlgprnt.cpp    
  dm.dll 6.0.8168.0 6.0.8447.0
  eafxis.lib    
  eafxisd.lib    
  eafxisd.pdb    
  expand.c    
  feacp.dll 12.0.8168.0 12.0.8447.0
  free.c    
  heapchk.c    
  heapinit.c    
  heapmin.c    
  isapi.cpp    
  libc.lib    
  libcd.lib    
  libcd.pdb    
  libcmt.lib    
  libcmtd.lib    
  libcmtd.pdb    
  link.exe 6.0.8168.0 6.0.8447.0
  malloc.c    
  mfc40.dll 4.0.0.5277 4.1.0.6140
  mfc40u.dll 4.1.0.6139 4.1.0.6140
  mfc42.dll 6.0.8168.0 6.0.8447.0
  mfc42.lib    
  mfc42.map    
  mfc42.pdb    
  mfc42d.dll 6.0.8168.0 6.0.8447.0
  mfc42d.lib    
  mfc42d.map    
  mfc42d.pdb    
  mfc42u.dll 6.0.8168.0 6.0.8447.0
  mfc42u.lib    
  mfc42u.map    
  mfc42u.pdb    
  mfc42ud.dll 6.0.8168.0 6.0.8447.0
  mfc42ud.lib    
  mfc42ud.map    
  mfc42ud.pdb    
  mfcapwz.dll 6.0.8168.0 6.0.8447.0
  mfcd42d.dll 6.0.8168.0 6.0.8447.0
  mfcd42d.lib    
  mfcd42d.map    
  mfcd42d.pdb    
  mfcd42ud.dll 6.0.8168.0 6.0.8447.0
  mfcd42ud.lib    
  mfcd42ud.map    
  mfcd42ud.pdb    
  mfcn42d.dll 6.0.8168.0 6.0.8447.0
  mfcn42d.lib    
  mfcn42d.map    
  mfcn42d.pdb    
  mfcn42ud.dll 6.0.8168.0 6.0.8447.0
  mfcn42ud.lib    
  mfcn42ud.map    
  mfcn42ud.pdb    
  mfco42d.dll 6.0.8168.0 6.0.8447.0
  mfco42d.lib    
  mfco42d.map    
  mfco42d.pdb    
  mfco42ud.dll 6.0.8168.0 6.0.8447.0
  mfco42ud.lib    
  mfco42ud.map    
  mfco42ud.pdb    
  mfcs42.lib    
  mfcs42.pdb    
  mfcs42d.lib    
  mfcs42d.pdb    
  mfcs42u.lib    
  mfcs42u.pdb    
  mfcs42ud.lib    
  mfcs42ud.pdb    
  msize.c    
  msvcrt.dll 6.0.8168.0 6.0.8397.0
  msvcrt.lib    
  msvcrt.pdb    
  msvcrt40.dll 4.21.0.0 4.22.0.0
  msvcrtd.dll 6.0.8168.0 6.0.8447.0
  msvcrtd.lib    
  msvcrtd.pdb for .dll    
  msvcrtd.pdb for .lib    
  nafxcw.lib    
  nafxcw.pdb    
  nafxcwd.lib    
  nafxcwd.pdb    
  nafxis.lib    
  nafxisd.lib    
  nafxisd.pdb    
  new.cpp    
  oleaut32.lib    
  oleauto.h    
  oledlgs2.cpp    
  psession.h    
  realloc.c    
  sbheap.c    
  shcv.dll 6.0.8168.0 6.0.8447.0
  sockcore.cpp    
  strex.cpp    
  strftime.c    
  tln0t.dll 6.0.8168.0 6.0.8447.0
  tzset.c    
  uafxcw.lib    
  uafxcw.pdb    
  uafxcwd.lib    
  uafxcwd.pdb    
  uuid.lib    
  viewcore.cpp    
  wincore.cpp    
  winfrm.cpp    
  winheap.h    
Visual FoxPro _app.vct    
  _app.vcx    
  _base.prg    
  _base.vct    
  _base.vcx    
  _controls.vct    
  _controls.vcx    
  _environ.vct    
  _environ.vcx    
  _framewk.dbf    
  _framewk.fpt    
  _framewk.h    
  _framewk.vct    
  _framewk.vcx    
  _gallery.vct    
  _gallery.vcx    
  _html.vct    
  _html.vcx    
  _htmlsty.vct    
  _htmlsty.vcx    
  _internet.vct    
  _internet.vcx    
  _menu.vct    
  _menu.vcx    
  _miscbtns.vct    
  _miscbtns.vcx    
  _movers.vct    
  _movers.vcx    
  _reports.vct    
  _reports.vcx    
  _table.vct    
  _table.vcx    
  _therm.vct    
  _therm.vcx    
  _ui.vct    
  _ui.vcx    
  _utility.vct    
  _utility.vcx    
  _webview.vct    
  _webview.vcx    
  activex.dep    
  appbldr.h    
  appbldr.prg    
  appbldr.sct    
  appbldr.scx    
  apphook.vct    
  apphook.vcx    
  appwiz.prg    
  appwiz.sct    
  appwiz.scx    
  browser.app    
  builder2.vct    
  builder2.vcx    
  builderd.cdx    
  builderd.dbf    
  builderd.fpt    
  builderd.vct    
  builderd.vcx    
  convert.app    
  coverage.app    
  fd3.fll 6.0.8161.0 6.0.8450.0
  fdkeywrd.cdx    
  fdkeywrd.dbf    
  foxhhelp.exe 6.0.8161.0 6.0.8450.0
  foxhhelpps.dll 6.0.8161.0 6.0.8450.0
  foxisapi.dll 6.0.8156.0 6.0.8450.0
  foxpro.h    
  fpole.dll 6.0.8161.0 6.0.8450.0
  fpole.ocx 6.0.8162.0 6.0.8450.0
  genhtml.prg    
  mdac_typ.exe 4.71.1015.0 21.1.3711.11
  registry.vct    
  registry.vcx    
  ribuildr.app    
  runcode.prg    
  vfp6.exe 6.0.8167.0 6.0.8492.0
  vfp6chs.dll   6.0.8492.0
  vfp6cht.dll   6.0.8492.0
  vfp6deu.dll   6.0.8492.0
  vfp6enu.dll 6.0.8167.0 6.0.8492.0
  vfp6esn.dll   6.0.8492.0
  vfp6fra.dll   6.0.8492.0
  vfp6kor.dll 6.0.8167.0 6.0.8492.0
  vfp6r.dep    
  vfp6r.dll 6.0.8167.0 6.0.8492.0
  vfp6rchs.dll   6.0.8492.0
  vfp6rcht.dll   6.0.8492.0
  vfp6rcze.dll   6.0.8492.0
  vfp6rdeu.dll   6.0.8492.0
  vfp6renu.dll 6.0.8167.0 6.0.8492.0
  vfp6resn.dll   6.0.8492.0
  vfp6rfra.dll   6.0.8492.0
  vfp6rkor.dll 6.0.8167.0 6.0.8492.0
  vfp6rrus.dll   6.0.8492.0
  vfp6run.exe 6.0.8167.0 6.0.8450.0
  vfp6t.dll   6.0.8492.0
  vfpcab.dll 1.0.0.1 1.0.0.2
  vfpglry.vct    
  vfpglry.vcx    
  vfpsp3.chm    
  wizard.app    
  wizard.dbf    
  wizard.fpt    
  wizbase.vct    
  wizbase.vcx    
  wizbtns.vct    
  wizbtns.vcx    
  www catalog.dbf    
  www catalog.fpt    
  wzform.app    
  wzimport.app    
  wzquery.app    
  wzreport.app    
  wzsetup.app    
  wzupsize.app    
  wzweb.app    
  xsource.zip    
Visual InterDev bldwizmg.dll 6.0.0.8159 6.0.0.8392
  button.asp    
  checkbox.asp    
  datagrid.asp    
  dtcrt.dll 6.0.0.8162 6.0.0.8450
  dtcserv.dll 6.0.0.8162 6.0.0.8450
  genproj.dll 7.0.8168.0 7.0.8450.0
  htmed.dll 6.0.0.8167 6.0.0.8428
  htmedui.dll 6.0.0.8167 6.0.0.8392
  label.asp    
  listbox.asp    
  mdac_typ.exe 4.71.1015.0 21.1.3711.11
  mmdtc.dll 6.0.0.8162 6.0.0.8450
  msde.dll 6.0.0.3005 6.0.84.50
  optiongrp.asp    
  pdm.dll 6.0.0.8169 6.0.0.8424
  pm.asp    
  recordset.asp    
  rsnavbar.asp    
  textbox.asp    
  triedit.dll 6.0.0.8167 6.1.0.8243
  urlpkr.dll 6.0.0.8159 6.0.0.8392
  viddbpkg.dll 6.0.0.8161 6.0.0.8450
  viddbui.dll 6.0.0.8159 6.0.0.8450
  vidisws.dll 6.0.0.8169 6.0.0.8450
  vidtc1.dll 6.0.0.8162 6.0.0.8450
  vidwebui.dll 6.0.0.8159 6.0.0.8450
  viwz1.dll 2.0.0.8160 2.0.0.8421
  viwz1ui.dll 6.0.0.8156 6.0.0.8450
  viwzrt.dll 2.0.0.8160 2.0.0.8421
Visual J++ appletht.vjp    
  classd.exe 5.0.2922.0 5.0.3176.0
  classr.exe 5.0.2922.0 5.0.3176.0
  comcontr.vjp    
  consappl.vjp    
  extwarn.txt    
  jactivex.exe 5.00.2918 5.0.3167.1
  javah.exe    
  javah.htm    
  javale.dll   6.0.0.8424
  jni.h    
  jps.dll 1.3.0.8167 1.3.0.8424
  jvc.exe 6.0.0.8167 6.0.0.8424
  mdm.exe 6.0.0.8149 6.0.0.8424
  msdbg.dll 6.0.0.8146 6.0.0.8424
  msjava.lib    
  msjavx86.exe 5.0.2922.0 5.0.3176.0
  msjvc.dll 6.00.8167 6.0.0.8424
  msvj98.dll 6.1.81.69 6.1.84.24
  msvj98ui.dll 6.1.81.67 6.1.83.49
  pdm.dll 6.0.0.8169 6.0.0.8424
  pkginst.exe 1.0.8173.1 1.0.8173.1
  scriptle.dll 6.0.0.8156 6.0.0.8424
  signcode.exe   5.101.1671.1
  signer.dll   5.101.1671.1
  vjreg.exe 6.0.0.8167 6.0.0.8424
  wfcdev.cer    
  wfcdev.zip    
Visual SourceSafe analyze.exe 6.0.81.69 6.0.8383
  ddconv.exe    
  ddupd.exe    
  ss.exe    
  ssapi.dll 6.0.81.69 6.0.8383
  ssarc.exe 6.0.81.69 6.0.8383
  ssgui.dll 6.0.81.63 6.0.8383
  ssrestor.exe 6.0.81.69 6.0.8383
Visual Studio acmsetup.exe 3.1.0.8043 3.1.0.8043
  autorun.inf    
  eula.txt    
  redist.txt    
  regsvr32.exe 4.0.1381.0 5.0.1641.1
  regtlib.exe    
  setup.exe 2.20.903.0 6.0.84.50
VSEE Repository insrepim.dll 6.0.8161.0 6.10.8253.0
  repodbc.dll 6.0.8161.0 6.10.9064.4
  reprc.dll 6.0.8161.0 6.10.8253.0