Help and Support

Article ID: 817411 - Last Review: April 3, 2007 - Revision: 4.1

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://support.microsoft.com/kb/815284/EN-US/ ) .
Expand all | Collapse all

SYMPTOMS

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.

CAUSE

This error occurs when there are multiple procedures with the same name in a module.

WORKAROUND

To work around this problem, delete the unwanted duplicate procedure. To do this, follow these steps:
  1. Open the form in Design view.
  2. 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.
  3. On the Debug menu, click Compile Database Name.

    You receive the following error message:
    Compile error: Ambiguous name detected: Procedure Name.
  4. Notice the procedure name, and then click OK.
  5. In the code, find the other occurrences of the Procedure Name procedure, where Procedure Name produced the compile error mentioned in step 3.
  6. Select and then delete the unwanted procedure.
  7. On the Debug menu, click Compile Database Name.
  8. On the File menu, click Close.

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
209907  (http://support.microsoft.com/kb/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
Keywords: 
kberrmsg kbprb KB817411

Article Translations