XL: Visual Basic Macro to Determine Which Button Was Selected

Last reviewed: December 1, 1997
Article ID: Q143345

The information in this article applies to:
  • Microsoft Excel for Windows 95, version 7.0
  • Microsoft Excel for Windows, versions 5.0, 5.0c
  • Microsoft Excel for the Macintosh, version 5.0, 5.0a

SUMMARY

In Microsoft Excel, you can create a Microsoft Visual Basic for Application macro to determine which button on a dialog box or a worksheet was clicked. You can do this by using the Caller property in conjunction with a Select Case statement.

MORE INFORMATION

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 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 needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. 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/refguide/default.asp

To create a macro that determines which button was clicked

  1. To open a new workbook, click New on the File menu.

  2. To create a new dialog sheet, click Macro on the Insert menu, and then click Dialog.

  3. On the dialog sheet, add three buttons by clicking the Create Button button on the Forms toolbar.

    Note the defined names that Microsoft Excel gives each button in the Names box (the box at the left end of the formula bar).

  4. To insert a new module, click Macro on the Insert menu, and then click Module.

  5. In the new Module sheet, enter the following code:

          ' Procedure to display which button was pressed.
    
          Sub WhichButton()
    
             ' Assign the calling object to a variable.
             ButtonName = Application.Caller
    
             ' Display the name of the button that was clicked.
             Select Case ButtonName
    
                ' NOTE: When you type the name of the button, note that
                ' Visual Basic is case and space sensitive when comparing                                                
                ' strings. For example, "Button 6" and "button6" are not the 
                ' same.
                Case "Button 6"
                MsgBox Application.Caller & "  was Clicked"
    
                Case "Button 7"
                MsgBox Application.Caller & " was clicked."
    
                Case "Button 8"
                MsgBox Application.Caller & " was clicked."
    
             End Select
    
          End Sub
    
    

  6. Switch to the dialog sheet.

  7. To assign the WhichButton procedure to each button on the dialog sheet, select the button, click Assign Macro on the Tools menu, select the WhichButton macro, and click OK. (Repeat this step for each button on the dialog sheet.)

To display the dialog sheet, click Run Dialog on the Tools menu.


Additional query words: 5.00 5.00c 7.00
Keywords : kbcode kbprg PgmHowto
Version : WINDOWS: 5.0, 7.0; MACINTOSH: 5.0, 5.0a
Platform : MACINTOSH WINDOWS
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.