Multiple Modules vs Sub-Procedures in a single Module

[bprisk]

I've got - in my humble opinion - a wonderful macro that I've developed with lots of searching and learning from this site. All of the code resides in "Module1" in a number of sub-procedures. I've seen other folks develop their code using multiple modules with essentially one sub-procedure in each module. Is there a benefit to either approach? Is there a "best practice" method? Or is it just personal preference?

I'm getting ready to dive into combining code in Access with some of the procedures I built into the Excel code, and would like to make the "new" program cleaner.

Thanks!

Brad

 

[francoisdublin]

It can make sense to group related macros in one module for clarity or because you can then copy the module to another workbook and have all those related macros together.
Another consideration is that some declarations you make at the start of your macros can be limited in scope to just the current module or public to all modules. When you make a declaration, the scope can also be on a macro-only level.

I wonder what others will say.