Rapid Application Development / Advanced Excel Development

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