One of the most popular methods of running a macro is having a button on the face of the worksheet. These are simple enough to create with the basic Form Controls found on the Developer Ribbon, which is what makes them a popular option.
But what if you had lots of buttons, all of which did a similar thing apart from a few different variables, arguments or parameters? One option is writing separate code for each button, or a second option maybe a big If statement to handle the logic for all the buttons. But please don’t do either of those, that would be crazy.
To pass an argument to a macro just requires the right syntax when assigning the macro to the button.
For the purposes of proving how this works, here is our example scenario. There are two Listboxes, each containing a list, with a button below each. Whenever the button is clicked, the count of items in the Listbox above it is displayed in a message box.
Lets consider how we can achieve this in the most efficient way possible.
Setting up the VBA code
I will assume you already know how to create a button and assign a macro to it.
If we had created separate code for each button, then the VBA code for clicking the button below the lstBox1 would be as follows:
Sub lstBoxCount() Dim ws As Worksheet Dim lstBoxName As String Dim lstBox As ListBox Set ws = Sheets("Sheet1") lstBoxName = "lstBox1" Set lstBox = ws.ListBoxes(lstBoxName) MsgBox lstBox.ListCount End Sub
If you notice, the sheet name and Listbox name are hardcoded into the macro, therefore we would need one macro for each button. Now imagine we had 30 Listboxes and 30 buttons… that would require 30 macros! Bad idea.
This is where arguments are useful. We can pass the worksheet name and Listbox name into the macro as arguments, by doing this, we can use a single piece of VBA code.
Sub lstBoxCount(wsName As String, lstBoxName As String) Dim ws As Worksheet Dim lstBox As ListBox Set ws = Sheets(wsName) Set lstBox = ws.ListBoxes(lstBoxName) MsgBox lstBox.ListCount End Sub
The code above can be used with any ListBox. There are no hardcoded variables within the code; they are passed to the code when it is called.
Running a macro with arguments
Having created a macro with arguments in the previous section, it raises a few new issues when assigning it to a button.
- The macro does not appear in the list of available macros. We can still use the macro, but we have to know it’s name.
- We need to know the right syntax to pass the arguments to the macro
We can handle both of these issue; no big deal.
The syntax required to a call a macro from the same workbook is:
'NameOfMacro "variable1", "variable2"'
Take careful note of where the single quotes, double quotes, commas and spaces are. There is nothing to help us complete this, apart from an error message to taunt us when we’ve got it wrong.
To call our lstBoxCount macro from above, the text in the Assign Macro window would be:
'lstBoxCount "Sheet1", "ListBox1"'
Where Sheet1 is the name of the worksheet and ListBox1 is the name of the first ListBox.
The same macro could be called from the second button, but the arguments would be different. Notice below the Listbox name has changed.
'lstBoxCount "Sheet1", "ListBox2"'
We can now use the same VBA code no matter how many Listboxes there are, or which worksheets they are on. We just change the values in the arguments.
Passing Numbers as arguments
If passing a number as an argument do not surround it in double quotes.
'NameOfMacro "textInQuotes", 1000'
Assigning a macro from another workbook
When returning to the Assign Macro window, you will notice Excel has added the name of the workbook into the Macro name box.
'Name of workbook.xlsm'!'lstBoxCount "Sheet1", "lstBox1"'
At first, this may seem annoying. But Excel is helping us here, as this is now displaying the syntax required to call a macro from another workbook.
'Name of worksheet.xlsm'!'NameOfMacro "variable1", "variable2"'
Running a macro with arguments based on a cell value
So far we have assumed we know the arguments when creating the buttons. That might not be the case; maybe the argument is based on a cell value. But that is OK too; we can dynamically pass a cell value into the macro at the point the button is clicked by assigning a macro using the following syntax.
'NameOfMacro "variable1", EVALUATE("A1")'
The example above assume the argument is contained in Cell A1. Once again, take careful note of where the single and double quotes are.
Using our specific example. Let’s assume the name of the Listbox is contained in Cell B2:
'lstBoxCount "Sheet1", EVALUATE("B2")'
This will work too! Cool, eh?
Wrapping it all up
Hopefully, you see this is very powerful and being able to set arguments based on a cell value is simply amazing. You no longer need lots of buttons. Instead, a drop-down box and one button might be sufficient.
About the author
Hey, I’m Mark, and I run Excel Off The Grid.
My parents tell me that at the age of 7 I declared I was going to become a qualified accountant. I was either psychic or had no imagination, as that is exactly what happened. However, it wasn't until I was 35 that my journey really began.
In 2015, I started a new job, for which I was regularly working after 10pm. As a result, I rarely saw my children during the week. So, I started searching for the secrets to automating Excel. I discovered that by building a small number of simple tools, I could combine them together in different ways to automate nearly all my regular tasks. This meant I could work less hours (and I got pay raises!). Today, I teach these techniques to other professionals in our training program so they too can spend less time at work (and more time with their children and doing the things they love).
Do you need help adapting this post to your needs?
I'm guessing the examples in this post don't exactly match your situation. We all use Excel differently, so it's impossible to write a post that will meet everybody's needs. By taking the time to understand the techniques and principles in this post (and elsewhere on this site), you should be able to adapt it to your needs.
But, if you're still struggling you should:
- Read other blogs, or watch YouTube videos on the same topic. You will benefit much more by discovering your own solutions.
- Ask the 'Excel Ninja' in your office. It's amazing what things other people know.
- Ask a question in a forum like Mr Excel, or the Microsoft Answers Community. Remember, the people on these forums are generally giving their time for free. So take care to craft your question, make sure it's clear and concise. List all the things you've tried, and provide screenshots, code segments and example workbooks.
- Use Excel Rescue, who are my consultancy partner. They help by providing solutions to smaller Excel problems.
Don't go yet, there is plenty more to learn on Excel Off The Grid. Check out the latest posts:
5 thoughts on “Assign macro with arguments to a Form Control button”
Go(o)d trick! Trick is compatible: *.xlsm / *.xls (until 2003) – no compatible: *.xlsb (variors error) – if convert: *.xls > *.xlsm … then reassign all “macro” parameters, because rename at convert action.
Thanks, that is useful to know.
This was extremely helpful to solve a problem, thank you. FWIW, Boolean arguments are like numbers and should also not be wrapped in quotes.
My specific example:
Then upon saving, Excel 365 added the workbook name:
What I don’t understand is why it is adding the workbook name, because it IS in the same workbook. Either way, it works, so thanks!
To automatic Excel function: full path, see above text: “Assign macro with arguments to a Form Control button”.
Curious if anyone else is seeing this. Used the above to pass a text string to a procedure via a form control button and it works fine. However after I save, close, reopen the area where I assigned the call with the argument has been prepended with the workbook name and clicking the button now fails. Behavior seems the same regardless of what the “Macros In” drop down is set to.