Error with Evaluate with More Than One Custom Function (153760)



The information in this article applies to:

  • Microsoft Excel for Windows 95 7.0a
  • Microsoft Excel for Windows 5.0c
  • Microsoft Excel for Windows NT 5.0
  • Microsoft Excel for the Macintosh 5.0a

This article was previously published under Q153760

SYMPTOMS

In the versions of Microsoft Excel listed above, when you use the Evaluate method to get the result of a formula, the call may return the following error value:
Error 2029 (#NAME)
followed by a run-time error of "Type Mismatch."

CAUSE

If you have multiple calls to a custom function, the Evaluate method may return an error value.

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. To work around this problem, break the Evaluate statement up into sections that only have one custom function call per section.

The following example takes the string "MyFunc()+MyFunc()" and illustrates how it could look using the workaround. Because MyFunc is a custom function call, it needs to be evaluated in two separate EVALUATE statements.

Sample Visual Basic Procedure

  1. Type the following code on a new module sheet:
          Sub Example()
              MsgBox Evaluate("MyFunc()") + Evaluate("MyFunc()")
          End Sub
    
          Function MyFunc()
              MyFunc = 1      ' Return a value of 1.
          End Function
    						
  2. Run the Example macro.

    Note that a message box with the number 2 is displayed.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem was corrected in Microsoft Excel 97 for Windows and Microsoft Excel 98 Macintosh Edition.

Modification Type:MinorLast Reviewed:10/10/2006
Keywords:kbbug kbcode kberrmsg kbfix kbProgramming KB153760