Controls should always be named, even if you are never going to refer to them in coding. Don't use the default names, e.g. Label1, Command1, Picture1, Text1, ...
Apply the general naming standards as discussed under General.
Use the same name for related items, e.g. A variable called "AccountNumber" would be displayed in a Text box called "txtAccountNumber" which is described by a label called "lblAccountNumber". (Don't use "AccountNum" in one and "AccNo" in another.)
Prefix all controls to identify their type. Below is a list of the most commonly used controls and their prefixes. If the prefixes in the list differ from standards that you are currently using, rather stick to your existing standard - it is more important to be consistent.
For some or other reason it is popular to differentiate between horizontal scrollbars and vertical scrollbars, as in hscLevel and vscLevel, even though they are exactly the same control with the "Orientation" property set to different values. This makes as much sense as prefixing all controls on the left side of the form with "L" and all controls on the right with "R", so I don't use it at all.
It doesn't add any value to distinguish between controls of different "flavours" or from different suppliers. For example, all my command buttons are prefixed with "cmd" regardless of whether they are the intrinsic VB controls or from the Sheridan 3D controls, or whatever third party creator. They are all in essence command buttons, so I use "cmd".
