The information in this article applies to:
SYMPTOMSIf the 16-bit version of Visual Basic is initially started or the Source Code Control Add-In check box is selected in the Visual Basic Add-In Manager when a standalone version of Visual SourceSafe has been installed under a 32-bit operating system, the following message and prompt results:
CAUSEThere are two possible causes:
-or- RESOLUTION
If the 16-bit version of the Visual SourceSafe client has not been loaded,
you need to uninstall the SourceSafe 32-bit client and then reinstall it
using the Custom option so that you can tell it to load the 16-bit as well
as the MS-DOS versions.
MORE INFORMATION
Visual SourceSafe 4.0, which ships with Visual Basic 3.0 Enterprise Edition
has a different Client setup (netsetup) from the standalone version.
Instead of two buttons (one for 32-bit and one for custom), there is only
one button (for all) that installs both the 16-bit and 32-bit versions of
Visual SourceSafe on 16- and 32-bit operating systems.
Additional query words:
Keywords : kbSSafe400 |
Last Reviewed: January 20, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |