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 Development Environment
In order to develop decent code, you need decent tools. The VBAIDE is certainly pretty tired looking these days, especially compared to Visual Studio 2010, but there are still some things we can do to improve on the default set up.
Fuller information is here, but in summary:
Option explicit
Don't warn about syntax errors
Actual set up - which windows are visible etc
Use a code library
Use MZ tools
Other tools - call tree, indenter, reference checker, BYG
Source control, even just exporting as text |
