Microsoft KB Archive/280607

= OFF2000: OnAction Property Code Doesn't Run As Expected When You Click Command Button =

Article ID: 280607

Article Last Modified on 1/29/2007

-

APPLIES TO


 * Microsoft Office 2000 Premium Edition
 * Microsoft Office 2000 Professional Edition
 * Microsoft Office 2000 Standard Edition
 * Microsoft Office 2000 Developer Edition
 * Microsoft Office 2000 Small Business Edition
 * Microsoft Excel 2000 Standard Edition
 * Microsoft Access 2000 Standard Edition
 * Microsoft FrontPage 2000 Standard Edition
 * Microsoft Outlook 2000 Standard Edition
 * Microsoft PowerPoint 2000 Standard Edition
 * Microsoft Word 2000 Standard Edition

-



This article was previously published under Q280607



SYMPTOMS
When you assign Microsoft Visual Basic code to run for a command button that is displayed in the Visual Basic Editor (not its corresponding Microsoft Office program) by using the OnAction property, the code does not run as expected when you click the command button. However, the same code assigned to a command button in any Office program runs as expected.



CAUSE
This behavior occurs because the Visual Basic Editor CommandBars object does not support the OnAction property. Therefore, the code does not run when you click the command button in the Visual Basic Editor.



WORKAROUND
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 Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

To work around this issue, use the CommandBarButton_Click event in a class module instead of the OnAction property. The following sample code illustrates how to create a command button in the Visual Basic Editor and then create a class module to respond to the Click event:  Start Excel. Click Tools, point to Macro, and then click Visual Basic Editor (or press ALT+F11).  Type or paste the following code in the module: Dim oBtns As New Collection

Function A Dim cb As CommandBar Dim oEvt As CBTnEvent

Set oBtns = Nothing Set cb = Application.VBE.CommandBars.Add(&quot;TestBar&quot;) cb.Visible = True cb.Position = msoBarTop

Set oEvt = New CBTnEvent Set oEvt.oBtn = cb.Controls.Add(msoControlButton) With oEvt.oBtn .Style = msoButtonIconAndWrapCaption .Caption = &quot;Test&quot; End With oBtns.Add oEvt End Function  On the Visual Basic Editor Insert menu, click Class Module. In the Properties window, change the class module name to CBTnEvent .  In the new class module, type or paste the following code: Public WithEvents oBtn as CommandBarButton

Private Sub oBtn_click(ByVal ctrl As Office.CommandBarButton, CancelDefault As Boolean) MsgBox &quot;Hello&quot; End Sub </li> Click anywhere in the code of function A, and then on the Run menu, click Run Sub/UserForm.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: OFF2000

Keywords: kbbug kbpending KB280607

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.