Using a Naming Convention
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Naming conventions are discussed here in terms of broad outlines only. The purpose of this discussion is to suggest an approach that will help you develop a consistent naming convention.
There are many formal naming conventions and each has its adherents and detractors. You can adopt one of the existing conventions or create one of your own. The important point is that you adopt some convention that would be self-evident to another Office developer and that you apply it consistently.
At a minimum, a useful naming convention will identify and distinguish variable type (object variable, control variable, and data type), variable scope, constants, and procedures, and it should be simple to understand and use. For an example of a naming convention you can adopt or that you can use as the basis for your own convention, see MCS Naming Conventions.doc in the ODETools\V9\Samples\OPG\Appendixes folder on the Office 2000 Developer CD-ROM.