MOD2000: Source Code Control File (Vssode.bas) Should Not Be Exported or Imported (234819)


The information in this article applies to:

  • Microsoft Office 2000 Developer
This article was previously published under Q234819

SYMPTOMS

The Multi-Code Import/Export add-in allows you to import and export the Vssode.bas file. However, this file contains source code control information unique to the current project, and the file exhibits incorrect behavior if you import it into another Visual Basic for Applications project.

CAUSE

Each application that is under source code control needs its own unique Vssode.bas file to maintain accurate source code control information about the objects in that application.

RESOLUTION

Do not import or export the Vssode.bas file to or from existing projects.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create and save a new workbook in Excel.
  2. Press ALT+F11 to open the Visual Basic Editor.
  3. Use the Add-in Manager to load the VBA Multi-Code Import/Export add-in and the VBA Source Code Control add-in.
  4. On the Add-ins menu, point to VBA Source Code Control, and then click Add Project to SourceSafe. If prompted, provide a valid user name and password.
  5. Add the current project to Visual SourceSafe, and add all of the objects in the workbook to source code control.
  6. Check Sheet1 out, make some changes, and check it back in.
  7. On the File menu, click Save projectname.
  8. On the Add-ins menu, click Multi-Code Export, and then move Sheet1 and Vssode from the Available Objects list to the Selected Objects list.
  9. Make a note of the folder that the files will be exported to, and then click Export. Vssode.bas and Sheet1.cls are exported to files.
  10. Create a new workbook.
  11. On the Add-ins menu, click Multi-Code Import. Browse to the folder that you noted in step 9, and import Sheet1 and Vssode.
  12. Note that the imported Sheet1 is named Sheet11, and it is not under source code control. Sheet1, Sheet2, and Sheet3 appear to be under source code control and have the history associated with the Sheets in the previous workbook.
Modification Type:MajorLast Reviewed:8/6/2002
Keywords:kbbug KB234819
©2002 Microsoft Corporation. All rights reserved.