It makes sense to use previously written VBA code when you're beginning a new Excel project.
This might include your own work, or procedures and methods you've come across that seem worthwhile to save for use at a later date.
This article will explain how to design your own code library without the use of plug-ins or other complicated tools.
All you need is a little knowledge of some standard VBA methods and procedures.
Designing The Code Library One issue associated with VBA is that you can't easily access code modules programmatically so you need to design a system to store your procedures.
A simple solution would be to save each procedure in a text file and keep references to the procedures in a worksheet.
So, the text file might be set up in the following way:
sub currentRegionSelect() ' code end sub sub listSort() 'code end sub And, in the worksheet you can keep information about the procedures which will be used to retrieve the code.
Something like this:
Title, Procedure Name, Description Select region, currentRegionSelect, Selects the cells around the active cell Sort list, listSort, Sorts a simple list alphabetically What You Need To Know To Create The Code Library With your data all set up, you can retrieve the code from the text file but you'll need to know about:

• The File System Object (FSO), to access the text file containing the saved procedures
• How to create a user form to give various options when retrieving code.
  
• Basic VBA methods such as cell and string manipulation to reference the saved procedures

Some options for the user form could include the following

• A list box from which the user can select any of the saved procedures in the text file
• An option to retrieve the code from the file and display in a text box
• Search facilities to find modules which contain various keywords, properties or methods

How you use a code library depends very much on your own coding style and the application you are developing.
It would be nice to think you can use the stored code without any editing but this would be rare and in reality you'll need to edit the code to fit the new procedure you're working on.
Hint: Print out a "cheat" sheet with the names and details of various code snippets you're likely to use on a regular basis.
That way, you can directly access the procedure you need by name rather than searching for it.
Summary Although developing a code library requires time and patience, it could pay dividends for anyone serious about developing their skills as a VBA developer.