WD97: CALL Statement Cannot Accept Variable Argument

WORKAROUND

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. If the variable strMacroName contains the name of the macro, use this statement:

   Application.Run strMacroName
				

Or, if you are using literal strings:

   Application.Run "Normal.Module1.MAIN"
 
   Application.Run "MyProject.MyModule.MyProcedure"
 
   Application.Run "'My Document.doc'!ThisModule.ThisProcedure"
				

If you specify the document or template name, your code can run macros only in documents or templates related to the current context; it cannot run any macro in any document or template.

Although Visual Basic code can call a macro directly (without using this method), this method is useful when the macro name is stored in a variable. The following two statements are functionally equivalent:

   <ProjectName>.<ModuleName>.<MacroName>
				

   Application.Run MacroName:="<ProjectName>.<ModuleName>.<MacroName>"

In cases where you call a literal string such as "AutoExec.Main", you must remove the quotation marks, as shown in the following example:

   CALL AutoExec.Main
				

NOTE: You cannot pass parameters to a macro by using the Run method.