WD98: Macro to Test for an Existing Macro Name (183147)

MORE INFORMATION

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers 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 requirements. When you write Visual Basic for Applications code, you may need to test for the existence of a macro before running it.

The following Visual Basic for Applications macro sample traps the errors described earlier. If the specified macro does not exist, the error trap can be used to branch selectively.

NOTE: Using this example, if the macro is found, the macro will run. If you want to test only for the existence of a macro, without running the macro, replace .Run = True with .Run = False.

   Sub DoesMacroExist()
      On Error Resume Next
      ' Use the Macro Dialog to run macro.
      With Dialogs(wdDialogToolsMacro)
         .Name = "xcallmacro"
         ' Attempt to run the macro.
         .Run = True
         .Execute
         ' If macro does not exist, an error will occur.
         If Err = 4633 Or Err = 4649 Then
            MsgBox "Macro not found."
         ElseIf Err = 0 Then
            MsgBox "Macro found."
         Else
            Err.Description
         End If
      End With
   End Sub
				

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