Blog posts

Looking for VBA developers (ideally, but not necessarily, existing users of VBE_Extras) who are willing to carry out some testing ... because while I consider myself an expert in VBA and in various other Office applications, I'm certainly not an expert when it comes to Visio or Project.

A declaration can have many references and sometimes you just want to go to the location of the next, or previous, reference of that declaration. That reference might be within the same procedure / property; it might be in the same Module but may or may not be visible on-screen; or it might be in another Module of your VBA Project. The "Next code reference in this Project" and "Previous code reference in this Project" commands of VBE_Extras will do this for you.

When you have a Module with many members (i.e. Module-level declarations such as Consts, Enums, Sub, Functions etc), it can sometimes be handy to just jump through each of those declarations in turn, in the order that they are present in the Module. That is the point of the "Goto declaration above" and "Goto declaration below" commands in VBE_Extras.

Maybe you're planning on making a change to your code that you're not entirely sure you will want to keep. Maybe it's just the end of a long day of development and you want to quickly make a copy of the Workbook / Document / Presentation / Database to a "backup" folder for safety. VBE_Extras lets you do this quickly, from within the VBE.

VBE_Extras allows you to customise its behaviour in many ways. Most of these "settings" are controlled via the Settings dialog (in the VBE's main menu, select: Extras > Settings). As of May 2026, there are 19 tabs with 151 settings in the Settings dialog. Here's how you can backup and restore those settings.

My bet is that few users of VBE_Extras are aware of, and regularly use, the two "Previous Lists" commands. However, they can be huge timesavers. The purpose of the Previous Lists commands is to re-show a list that has been shown previously. Clear? No, I don't think. This blog post will explain ...

If the cursor is on a declaration, or on a reference of a declaration, then the "References for code at cursor" command will display a dialog with a list of all references of that declaration (including the declaration itself). So it could be every place that a variable is referenced. Or every place that a procedure is referenced. Or a constant. Or an Enum, a Type ... or any other type of declaration.

Getting information about the code at the cursor ... for declarations in your VBA Project, and things declared outside of your VBA Project

Ever wanted to know how many procedure or properties there are in your Project? Or how many code / comment / blank lines? Or how many of those lines are declaration lines? The the Project Stats command is for you.

VBE_Extras will show a dialog containing a list of all declarations from any procedure/property, Module or VBA Project.