XL: Function Name Can't be Same as Module Name

Last reviewed: February 2, 1998
Article ID: Q105571

The information in this article applies to:
  • Microsoft Excel for Windows, versions 5.0, 5.0c
  • Microsoft Excel for the Macintosh, version 5.0, 5.0a
  • Microsoft Excel for Windows 95, versions 7.0, 7.0a
  • Microsoft Excel 97 for Windows
  • Microsoft Excel 98 Macintosh Edition

SYMPTOMS

In the versions of Microsoft Excel listed above, if you attempt to run a function that has the same name as a Visual Basic module, and the Visual Basic module is located in the same workbook as the function, you may receive one of the following error messages:

   Expected procedure, not module

   -or-

   Microsoft Excel cannot find '<function name>' on <workbook name>.

WORKAROUND

Instead of creating a function, create a Sub procedure. A Sub procedure can have the same name as a module without causing an error.

Note that Sub procedures cannot be called from worksheet formulas.

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 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 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/default.asp

You may receive an error message if you run a function called "Test1" if that function is located in a Visual Basic module in a workbook that also contains a module named "Test1".

Example

  1. In a new workbook, insert a new Visual Basic module and name it "Test1" (without the quotation marks).

  2. In Test1 (the module that you just inserted), type the following function:

          Function Test1()
    
              TestVar = 1
          End Function
    
    

  3. In cell A1 of a new worksheet in the same workbook, type the following formula:

          =Test1()
    

       You may receive the error message "Expected procedure, not module". A    
    
#NAME! error value is returned to cell A1.

  1. In cell A1 of a new worksheet in a different workbook, enter the formula:

          =Book1!Test1()
    

    You may receive an error message. A #NAME! error value appears in cell A1.


Additional query words: 5.00 5.00a 5.00c 7.00 7.00a XL98 XL97 XL7 XL5
Keywords : kbcode kbprg PgmOthr
Version : WINDOWS:5.0,5.0c,7.0,97; MACINTOSH:5.0,5.0a,98
Platform : MACINTOSH WINDOWS
Issue type : kbprb
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 2, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.