WD2000: Cannot Trap Undefined Sub or Function Error (212607)

MORE INFORMATION

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 a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site: For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site: For more information about how to use the sample code in this article, click the article number below to view the article in the Microsoft Knowledge Base: An undefined Sub or Function procedure is an attempt to call a Sub or Function procedure that does not exist.

The following sample Visual Basic for Applications macro makes a call to the non-existent function MyFunction. The error message described in the "Summary" section occurs before the macro begins to run or compile.

Sub MyMacro()
   On Error Resume Next
   x = MyFunction()
End Sub
				

Error trapping does not work with undefined subroutines, functions, or commands. To avoid these type of errors, the macro must be designed so that it does not call an undefined subroutine, function, or command. Specifically, when you create your macro, make sure that the following conditions are satisfied:

• The Sub procedure or Function exists.
• The Sub procedure or Function is not misspelled.
• The Sub procedure or Function is not declared as Private.
• If the Sub procedure or Function exists in a custom template or document project other than the project in which the calling routine exists, make sure that a reference has been added to the custom template project or document.
  
  NOTE: You cannot add a reference to a project in a document whose underlying template is the same template as the calling procedure.

Adding a Project Reference

To add a project reference, follow these steps:

1. On the Tools menu, click References to display the References dialog box.
2. The References dialog box shows all object libraries and projects registered with the operating system. Scroll through the list for the project that you want to reference. If the template or document project isn't listed, use the Browse button to search *.dot or *.doc files.
   
   References whose check boxes are selected are used by your project; those that aren't selected are not used, but can be added.
3. Select the Project reference in the Available References list in the References dialog box, and then click OK.
   
   NOTE: If a project has not been saved, it appears as

   UNSAVED: Project Name

   and you are unable to make a reference to it.

For more information about References, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type references command (tools menu) in the Office Assistant or the Answer Wizard, and then click Search to view the topic.