Naming convention for VBA modules?

Question

I never know what to call VBA modules. Should I:

• Use a prefix like basName or modName.
• Do not use a prefix, such as a module. (But avoid limited words)
• Something else

Answer 1

Not a prefix! Name the module appropriately for what it does.

Answer 2

Of course, this takes the car back, but when I did extensive VBA development, I always called my modules a prefix of something like "bas", because the names of the class modules and Global modules in combination had to be unique (i.e. you there could not be a global module named Foo and a Class module named Foo). I think the same goes for VB6, but that was many years ago.

Answer 3

I prefix standard modules with M, class modules with C, and custom forms with U. In VBE, I turn off the folder view in the project explorer to show all the modules. Prefixes keep them beautifully sorted.

Answer 4

The prefix can be useful only so that neighboring modules are displayed next to each other in the project window. I use prefixes like "numeric" or "test" all the time instead of another way to group them. But you probably don't need something like a “mod” ...