DOCUMENT:Q190211  07-AUG-1998  [vbwin]
TITLE   :PRB: Problems With Visual Basic 5.0 and 6.0 on Same System
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:5.0,6.0
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Learning, Professional, and Enterprise Editions
   for Windows, versions 5.0, 6.0
---------------------------------------------------------------------

SYMPTOMS
========

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

MORE INFORMATION
================

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.

Additional query words: kbDSupport kbSetup kbConfig kbVBp500 kbVBp600 kbdss
======================================================================
Version           : WINDOWS:5.0,6.0
Platform          : WINDOWS
Issue type        : kbprb

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1998.