Please Note: This article is written for users of the following Microsoft Excel versions: 97, 2000, 2002, and 2003. If you are using a later version (Excel 2007 or later), this tip may not work for you. For a version of this tip written specifically for later versions of Excel, click here: Debugging a Macro.
Written by Allen Wyatt (last updated March 6, 2021)
This tip applies to Excel 97, 2000, 2002, and 2003
In Excel, macros are written in a language called Visual Basic for Applications, or VBA. When you write a macro, you need to test it and correct any errors in the macro. This process is called debugging. The process of debugging a macro in VBA is the same as debugging in any other programming language. All you need to do is step through the macro, one command at a time, and make sure it works as you think it should. You do this by viewing both the windows for your macro and a test worksheet. As you step through the macro (using the commands available in the Debug menu of the VBA Editor), you can correct any errors you locate. (I particularly like to use the F8 key to step through the macro one line at a time.)
As you are debugging macros, you need to make sure you think through every possible way the macro could be used and all the possible conditions that could exist at the time the macro is invoked. Try the macro out in all these ways and under all these conditions. In this way, you will make your macro much more useful.
Don't be surprised, however, if you give your workbook to some friends and they discover bugs you never thought of. In those cases, the debugging process is the exact same as mentioned above—except you use their data as your test worksheet. Try to go through the macro using their data, one line at a time, until you discover where your code went wrong and then fix it.
Note:
ExcelTips is your source for cost-effective Microsoft Excel training. This tip (2310) applies to Microsoft Excel 97, 2000, 2002, and 2003. You can find a version of this tip for the ribbon interface of Excel (Excel 2007 and later) here: Debugging a Macro.
Program Successfully in Excel! John Walkenbach's name is synonymous with excellence in deciphering complex technical topics. With this comprehensive guide, "Mr. Spreadsheet" shows how to maximize your Excel experience using professional spreadsheet application development tips from his own personal bookshelf. Check out Excel 2013 Power Programming with VBA today!
One of the powerful programming structures available in VBA is the Select Case structure. This tip explains how you can ...
Discover MoreExcel is great for collecting all sorts of information. You might even use it to create a catalog of your photos. Working ...
Discover MoreWhen creating macros, it is often necessary to change from one type of data to another. Here's how you can change from a ...
Discover MoreFREE SERVICE: Get tips like this every week in ExcelTips, a free productivity newsletter. Enter your address and click "Subscribe."
There are currently no comments for this tip. (Be the first to leave your comment—just use the simple form above!)
Got a version of Excel that uses the menu interface (Excel 97, Excel 2000, Excel 2002, or Excel 2003)? This site is for you! If you use a later version of Excel, visit our ExcelTips site focusing on the ribbon interface.
FREE SERVICE: Get tips like this every week in ExcelTips, a free productivity newsletter. Enter your address and click "Subscribe."
Copyright © 2025 Sharon Parq Associates, Inc.
Please Note:
This article is written for users of the following Microsoft Excel versions: 97, 2000, 2002, and 2003. If you are using a later version (Excel 2007 or later), this tip may not work for you. For a version of this tip written specifically for later versions of Excel, click here:
Comments