Visual Basic naming rules
Use the following rules when you name procedures, constants, variables, and arguments in a Visual Basic module:
You must use a letter as the first character.
You can't use a space, period (.), exclamation mark (!), or the characters @, &, $, # in the name.
Name can't exceed 255 characters in length.
Generally, you shouldn't use any names that are the same as the function, statement, method, and intrinsic constant names used in Visual Basic or by the host application. Otherwise you end up shadowing the same keywords in the language. To use an intrinsic language function, statement, or method that conflicts with an assigned name, you must explicitly identify it. Precede the intrinsic function, statement, or method name with the name of the associated type library. For example, if you have a variable called
Left, you can only invoke the Left function by using
You can't repeat names within the same level of scope. For example, you can't declare two variables named
agewithin the same procedure. However, you can declare a private variable named
ageand a procedure-level variable named
agewithin the same module.
Visual Basic isn't case-sensitive, but it preserves the capitalization in the statement where the name is declared.
Support and feedback
Have questions or feedback about Office VBA or this documentation? Please see Office VBA support and feedback for guidance about the ways you can receive support and provide feedback.