Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 817411 - Last Review: September 17, 2011 - Revision: 5.0
Error message when you run a procedure in Access: "Ambiguous name detected"
Moderate: Requires basic macro, coding, and interoperability skills.
For a Microsoft Access 97 version of this article,
see
815284Â
(http://kbalertz.com/Feedback.aspx?kbNumber=815284/EN-US/
)
.
When you run a procedure in Microsoft Access 2000 or later,
you may receive the following error message:
The
expression Event_Name you entered as the event
property setting produced the following error: Ambiguous name detected:
EventProcedure_Name.
This error occurs when there are multiple procedures with
the same name in a module.
To work around this problem, delete the unwanted duplicate
procedure. To do this, follow these steps:
- Open the form in Design view.
- In
Microsoft Office Access 2003, click Code on
the View menu.
In
Microsoft Office Access 2007, click
View Code in the Tools group on the Design tab. - On the Debug menu, click Compile
Database Name.
You receive the
following error message: Compile error: Ambiguous name
detected: Procedure Name.
- Notice the procedure name, and then click
OK.
- In the code, find the other occurrences of the
Procedure Name procedure, where
Procedure Name produced the compile error mentioned
in step 3.
- Select and then delete the unwanted procedure.
- On the Debug menu, click Compile
Database Name.
- On the File menu, click
Close.
For additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
209907Â
(http://kbalertz.com/Feedback.aspx?kbNumber=209907/EN-US/
)
ACC2000: Compile Error After Converting Form Macros to VBA
APPLIES TO
- Microsoft Office Access 2007
- Microsoft Office Access 2003
- Microsoft Access 2002 Standard Edition
- Microsoft Access 2000 Standard Edition
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