Codematic Excel developers logo
Codematic spreadsheet-excel development image

Rapid Application Development / Advanced Excel Development

Products for Excel
Commercial Products:
  - Classic Ribbon
  - Alt-FileSearch
  - Password Remover
Spreadsheet Quality Products
Free Products
Excel Development
Excel Development Index
Excel VBA
- VBA IDE (editor)
- VBA Training
- VBA Best Practice
- VBA Performance
- COM Performance
- VBA Security
Excel and Databases
Excel and Pivot Tables
Excel Add-ins
Worksheet Functions
Excel and xlls
Excel (in)security
Excel testing
Excel and .net
Excel External Links
Excel Developer Types
Professional Excel Development
Excel 2007
Excel 2010
Excel Development Archive
Spreadsheet Services
Spreadsheet Development
Spreadsheet Migration
Spreadsheet Maintenance
Spreadsheet Review
Spreadsheet Management
Excel User Confs
Consultant Profile
Book Reviews
Site Map

VBA Best Practice

There is a lot of information floating around about how to get various things done in VBA, how to make the best use, or sometimes just the most use of VBA and Excel.
This section aims to add an element of Quality and Best Practices. These are just general guidelines, a professional developer will always assess the options and make the appropriate choice in their specific situation.
These suggestions are specific to Excel VBA in commercial settings, many will not translate to other technologies or other settings.

VBA Best Practice Series

High Quality Code - General 1

Naming convention:

  • Option 1 fit in with current standards (eg Reddick 3 letter)
  • Option 2 give everything a simple, distinctive, non abbreviated descriptive name
  • Procedures - verb noun combination
  • Variables - add scope prefix, data type maybe, usage more useful - eg m_rwCustomer for row in customer table or colMonth for month column.
  • Only use a type prefix if you know what it is doing for you and you value that. (eg probably don't need 'obj')
  • Codematic naming convention is here
  • Avoid most comments - make meaning crystal clear in the code.
  • Move non standard code and workarounds to named routines, and comment if necessary
  • refactor early and often
  • build test routines as you go, and at least step through in the debugger.

    Upcoming Events:

    25 January 2012 - UK Excel Developer Conference - London

    Products for sale:


    Office 2007 FileSearch replacement logo

    New information about the missing FileSearch feature in Office 2007 and details of our pragmatic solution (Current price GBP 30.00)


    worksheet password remover logo

    Instant Excel worksheet protection remover and password recovery (Current price GBP 15.00)

    Classic Ribbon Tab

    classic ribbon for office 2007 logo

    Add Excel 97/2000/2002/2003 compatible menu structure to Excel 2007
    (Current Price GBP 10.00)


    Products coming soon:

    Link Manager

    (Find and control external links in Excel Workbooks)

    Due by Q1 2111.

    XLAnalyst Pro

    (Excel VBA based spreadsheet auditing tool)

    Due before the end of 2111.

    This page was last reviewed on December 21, 2011

    ©Codematic Ltd 1999-2011