XL97: Run-time Error Using Copy Method to Copy Module Sheet

ID: Q189003

The information in this article applies to:

SYMPTOMS

When you attempt to copy a Microsoft Visual Basic for Applications module sheet in a Visual Basic macro procedure, you may receive the following error message:

   Run-time error '9':
   Subscript out of range

CAUSE

This problem may occur if the following conditions are true:

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

   http://www.microsoft.com/support/supportnet/refguide/

The following sample macro illustrates how to copy the contents of a module to a new code module contained in another workbook. This example assumes that you have a workbook open that contains two modules.

1. Start the Visual Basic Editor (press ALT+F11).

2. If Project Explorer is not visible, press CTRL+R to activate Project

   Explorer.

3. Click to select the Visual Basic project that contains the module sheet
   that you want to copy.

4. On the Tools menu, click References. Click to select the "Microsoft
   Visual Basic for Applications Extensibility" check box and then click
   OK.

5. Click Module on the Insert menu.

6. Type the following code into the module sheet:

   Sub CopyModule()
      Dim CodeLines As String
      Dim ModuleToCopy As VBComponent
      Dim NewModule As VBComponent

      ' Set a variable to the module to copy.
      ' Note: This assumes that the name of the module to copy is
      ' "module2". Replace "Module2" with the name of the module to copy.
      Set ModuleToCopy = _
             Application.VBE.ActiveVBProject.VBComponents("module2")

      ' Get the Visual Basic code from the module.
      CodeLines = ModuleToCopy.CodeModule.Lines _
                 (1, ModuleToCopy.CodeModule.CountOfLines)

      ' Create a module sheet in another workbook.
      ' Note: You must refer to the name of the Visual Basic project. By
      ' default, the name of all new projects is "VBAProject". You may want
      ' to rename the project to which you are copying the contents of the
      ' module sheet.
      Set NewModule = Application.VBE.VBProjects("VBAProject") _
                      .VBComponents.Add(vbext_ct_StdModule)

      ' Add the Visual Basic code to the new module.
      NewModule.CodeModule.AddFromString CodeLines

      ' Rename the new module to the name of the previous module.
      NewModule.Name = ModuleToCopy.Name

   End Sub

7. Run the CopyModule procedure.

Excel will insert a new module sheet into the Visual Basic project named VBAProject, and will copy the code from the module named Module2 in the active Visual Basic project.

MORE INFORMATION

For additional information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q165304
   TITLE     : XL97: Modules Inserted Manually Are Not in Modules
               Collection

Additional query words: XL97
Keywords          : kberrmsg kbdta kbdtacode xlvbmigrate 
Version           : WINDOWS:97
Platform          : WINDOWS
Issue type        : kbprb
Solution Type     : kbnofix

Last Reviewed: May 17, 1999