The information in this article applies to:
SYMPTOMSModerate: Requires basic macro, coding, and interoperability skills.
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 professionals 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 a Microsoft Certified Solution Provider or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Solution Providers, please see the following page on the World Wide Web: http://www.microsoft.com/mcsp/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/overview/overview.asp CAUSEAt 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. Method 1If 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:
Method 2You can open the object's class module in Design view and remove the duplicate procedure:
MORE INFORMATIONWhen 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 BehaviorThe following example uses a form. You can obtain the same results by using a report.
REFERENCESFor more information about using the Covert Macros to Visual Basic command, in the Visual Basic Editor, click
Microsoft Visual Basic Help on the Help menu, type "converting macros" in
the Office Assistant or the Answer Wizard, and then click Search to
view the topic. Additional query words: prb
Keywords : kbdta FmsEvnt |
Last Reviewed: July 6, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |