FIX: Problems Saving Visual Basic Form to Visual SourceSafe (223128)


The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows 5.0
  • Microsoft Visual SourceSafe for Windows 6.0
  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Professional Edition for Windows 6.0
  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q223128

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.
causes a "Save as Dialog" to display and you are prompted to overwrite the existing file.

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 that this is a bug in the Microsoft products that are 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:

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

194295 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.
Modification Type:MajorLast Reviewed:10/15/2002
Keywords:kbBug kbVS600sp3fix KB223128
©2002 Microsoft Corporation. All rights reserved.