Microsoft KB Archive/209907

= ACC2000: Compile Error After Converting Form Macros to VBA =

Article ID: 209907

Article Last Modified on 10/11/2006

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q209907



Moderate: Requires basic macro, coding, and interoperability skills.



SYMPTOMS
After you convert macros to Visual Basic for Applications code in a form or report by using the "Convert Macros to Visual Basic" command, you may receive the following error message when you use the form or report.

The expression  you entered as the event property setting produced the following error: Ambiguous name detected: .

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.



CAUSE
At one time, the form or report had an event procedure that was later changed to a macro.



RESOLUTION
To prevent the error, open a form or report class module in Design view and delete the procedure for the event whenever you replace an event procedure with a macro.

To resolve the error, use one of the following methods to remove the duplicate procedure in the object's class module.

Method 1
If the object does not contain a mixture of Visual Basic code and macros, you can remove the object's class module before you convert its macros:


 * 1) Open the form or report in Design view.
 * 2) Set the object's HasModule property to No, and then save the object.

NOTE: Any Visual Basic code that the object contains is removed along with its class module when you set the HasModule property to No.
 * 1) On the Tools menu, point to Macro, and then click Convert Form's Macros to Visual Basic or Convert Report's Macros to Visual Basic.

A new class module is created for the object and no duplicate procedure names exist.

Method 2
You can open the object's class module in Design view and remove the duplicate procedure:  Open the object in Design view. On the View menu, click Code. On the Debug menu, click Compile . You will receive the following error message:

Ambiguous name detected: .

 Look through the class module, looking for another procedure with the same name as the one that produced the compile error.</li> Select and delete the unwanted procedure.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
When you replace [Event Procedure] with the name of a macro in Design view of a form or report, the procedure itself remains in the object's class module. When you convert the macro to a Visual Basic procedure, the wizard does not check to see if a procedure for that event already exists, and it creates a duplicate procedure.

Steps to Reproduce Behavior
The following example uses a form. You can obtain the same results by using a report. <ol> Start Microsoft Access and open the sample database Northwind.mdb.</li> Create the following new macro called TestVBA: </li> Save the macro and close it.</li> Use the AutoForm: Columnar Wizard to create a new form based on the Shippers table.</li> Save the form as frmShippers, and then open it in Design view.</li>  Set the OnLoad property of the form to the following event procedure: Private Sub Form_Load 'This module will be replaced by a macro End Sub </li> Close the form's Module window.</li> Change the OnLoad property of the form from [Event Procedure] to TestVBA.</li> On the Tools menu, point to Macro, and then click Convert Form's Macros to Visual Basic.</li> In the Convert Form Macros dialog box, click Convert.</li> Click OK when the conversion finishes and switch the form to Form view.</li></ol>

NOTE: You receive the error message indicated in the Symptoms section. If you browse the form's class module, you will find two procedures named Form_Load.

<div class="references_section">