FIX: Problems Saving Visual Basic Form to Visual SourceSafe

• Microsoft Visual SourceSafe, 32-bit, for Windows versions 5.0, 6.0
• Microsoft Visual Basic Professional and Enterprise Editions for Windows, versions 5.0, 6.0

SYMPTOMS

Saving a form that was previously saved that meets the following criteria:

• The form contains an ActiveX control.



• The form was checked out from Visual SourceSafe.

CAUSE

This problem occurs when you check out a form without checking out the .vbp file first.

RESOLUTION

To work around this, checkout the .vbp file first, then checkout the other files.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.This bug was corrected in Visual Studio 6.0 Service Pack 3. For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed

MORE INFORMATION

Steps to Reproduce Behavior

1. Open a new Standard EXE project. Form1 is created by default.



2. Add an ActiveX control to Form1 (for example, a progress bar).



3. Add the project and the form to Visual SourceSafe.



4. Check in the .vbp file.



5. Check out the form and make a change to it.



6. Save the form.

Additional query words:

Keywords : kbservicepack kbSSafe kbSSafe500 kbSSafe600 kbVBp600bug kbGrpVB kbVS600sp2 kbVS600SP1 kbVS600sp3fix
Version : WINDOWS:5.0,6.0
Platform : WINDOWS
Issue type : kbbug