Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 210098 - Last Review: July 14, 2004 - Revision: 1.1
ACC2000: Same Named Module and Procedure Causes Errors
This article was previously published under Q210098
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).
When you run a procedure from an object's events, you may receive the following error message:
The expression [event name] you entered as the event property setting produced the following error: The expression you entered has a function name that Microsoft Access can't find.
If you use the RunCode action in a macro to call a function, you may receive the following error message:
The expression you entered has a function name that Microsoft Access can't find.
If you try to run a procedure from the Immediate window, you may receive the following error message:
Compile Error:
Expected variable or procedure, not module.
NOTE: All the modules in the database or project will appear to compile successfully.
A user-defined function or a subroutine have the same name as a module. These errors occur even if the procedure is not contained in the module with the same name.
Change the name of the module so that it is different from the name of any
procedure that you have in the database or project.
Steps to Reproduce Behavior
- Create a new Microsoft Access database, and then create a module.
- Type the following procedure:
Function Test()
MsgBox "Does this work correctly?"
End Function
- Save the module as Test.
- Type the following line in the Immediate window, and then press ENTER:
APPLIES TO
- Microsoft Access 2000 Standard Edition
| kberrmsg kbprogramming kbprb KB210098 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate