Adding modules to the library

Most programmers at some point start collecting modules containing solutions they previously used succesfully, with the purpose of later using them again. Code VBA provides a library feature which makes it possible to save your modules in an organized way.

Code modules may contain one or more procedures that can function independently. Some solutions however require a combination of modules and een code snippets.

Adding a single module

To add a module in your current project to the library:

Clean up the module so that it has a clearly defined purpose and only contains procedures for that;
Give the module a suitable name;
In the Code Explorer right-click the module to export and select 'Export file';
Chosing a location in the \VBA Code folder most suitable to store the module.

Example: modStringFunctions

A collection of common String manipulation functions is in the \VBA\String subfolder of the Code VBA library. As such, it functions are accessible from the VBA » String menu.

The VBA Strings Library menu shows all available String related snippets and procedures

Visibility All public procedure in a module inserted in a Code Library subfolder appear in the menu of the selected location. By make certain procedures Private you can hide them.

Looking at the tooltip of the procedure StringContains we see a title that indicates what behaviour we may expect.

Procedure tooltip caption To add a tooltip caption, put a single comment line directly under the procedure header.

Procedures that operate on Objects

The image below, showing the Code Library folder hierarchy, the folder of Workbook is opened. The right pane shows which modules are inside. It seems logical to have modWorkbookFindProcedures or modRangeNameProcedures in there, containing procedures related to Finding (ranges). But why is modSheetIsProcedures in this folder, and not in folder \Worksheet? The reason is the modules contains procedures, such as IsValidSheetName, that don't work on a Worksheet object, but are useful in the context of a Workbook object.

Chosing a location to store a module

The Code VBA library already has a structure reflecting VBA and Office application's Objects. We suggest you follow this design, when adding modules.

Code Library structure Inspect the Code Library folder hierarchy and what it already contains to get an idea how to best use it.

Updating the module If there already is a module with the current name, the folder containing that will be preselected. You can then overwrite the file, e.g. replacing it with a newer version or decide to give your module a new name. In the latter case you must Cancel the export and change the module name (2.).

module Attribute VB_Name vs filename Make sure to keep the name of the module Attribute VB_Name equal to the filename. If you don't, at some point there may occur conflicts when using a procedure from the library: module name must match filename

it does not recognize module containing the procedure is already present, inserting it a second time causing compile error;
it wrongly assumes the module is already present and does not add the module.