PRB: Problems With Visual Basic 5.0 and 6.0 on Same SystemID: Q190211
|
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.
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:
Additional query words: kbDSupport kbSetup kbConfig kbVBp500 kbVBp600 kbdss
Keywords :
Version : WINDOWS:5.0,6.0
Platform : WINDOWS
Issue type : kbprb
Last Reviewed: May 11, 1999