Whether you are naming variables, forms, controls or tables, there are certain guidelines to follow when thinking up a name for the item in question. Now we are not talking about prefixes or suffixes, scope and data type, we are talking about the actual name part, the "body" of the name.
Always use "Option Explicit" as the first line of ALL your code modules. To have VB insert this line automatically for you, go to the "Tools" menu, select "Options", and then select the "Editor" tab on the form that pops up. Make sure that the "Require Variable Declaration" checkbox is checked.
Names must be descriptive. E.g. "Number" does not give enough information, "CustomerNumber" does. Creating a variable called "X", "i" or something similar is just laughably stupid, and in some countries it's a capital offense.
Names must be concise, i.e. "FirstInitialCustomerFinancialTransactionRecordNumber" is as bad as "X".
Don't use abbreviations, i.e. use "CustomerCode" as opposed to "CustCode"
Use capitalization to "separate" words, e.g. use "FileCodeCount" as opposed to "filecodecount" or "FILECODECOUNT".
Don't use underscores. "CustomerCode" is better than "Customer_Code"
Always use exactly the same name for the same item, e.g. a variable called "CustomerCode" will be displayed in a text box called txtCustomerCode. The label above the text box will be named lblCustomerCode. Not CustomerNumber, or Customer, or Code or anything else. If it's CustomerCode in one place, it must be CustomerCode everywhere.
