PRB: Problems When Visual Basic 5.0 and 6.0 Are Installed on the Same System

Installing Visual Basic 6.0 on a computer without uninstalling the existing Visual Basic 5.0 may cause both products to function improperly. This article describes some of the possible problems that can occur.

Because Visual Basic 5.0 and Visual Basic 6.0 employ the same license keys and names for some files, conflict can arise if a machine has both of them installed.

After installing Visual Basic 6.0 on a machine that already has Visual Basic 5.0 installed, both the Application Performance Explorer (APE) and the T-SQL Debugger in Visual Basic 5.0 will not work properly. Please see Scenario 3 below for more information.

Visual Basic 6.0 will work without noticeable problems. Although the Add-In Manager DialogBox will list duplicated entries, these entries are distinguishable by Visual Basic 5.0 and Visual Basic 6.0. If Visual Basic 5.0 is uninstalled, the following components will no longer work properly in Visual Basic 6.0:

• APE
• Visual Data Manager (Visdata)
• T-SQL Debugger
• Remote Data Control (MSRDC)

If Visual Basic 6.0 is uninstalled, APE, Visdata, and API Viewer might not work properly in Visual Basic 5.0.

Following are scenarios of some possible problems:

Scenario 1

1. Install Visual Basic 5.0.
2. Install Visual Basic 6.0.
3. In the Control Panel, select Add/Remove Programs, and then select Visual Basic 5.0 for Removal. Note that the APE, VisData, and T-SQL Debugger are not working, and MSRDC reports that it loses its license to run.

Scenario 2

1. Install Visual Basic 5.0.
2. Install Visual Basic 6.0.
3. In Control Panel, select Add/Remove Programs, and then select Visual Basic 6.0 for Removal. Note that the APE, Visdata, and API Viewer do not work properly.

Scenario 3

1. Install Visual Basic 5.0.
2. Install Visual Basic 6.0.
3. Run Visual Basic 5.0 and start APE. An error message is received about an incorrect version of aesvrmgr.exe.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base: