Form module vrs Standard modules
I think you may be trying to make it too complicated. Remember OOP principles. Keep object methods and properties together. An object can be something abstract too. Think of a module as a "code container object". Organize your code by putting it in the proper container. For more info on the differences between module types, see my reply in this thread.
When you create a class or form, you are making a new object. If a procedure you want to write isn't part of that object's character, put it in a standard module.
When you make a standard module, its more of an abstract container object. I usually don't have too many of those, unless you want to organize your code and sub-categorize, with a module for each category, e.g. modPrintFunctions.
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
When you create a class or form, you are making a new object. If a procedure you want to write isn't part of that object's character, put it in a standard module.
When you make a standard module, its more of an abstract container object. I usually don't have too many of those, unless you want to organize your code and sub-categorize, with a module for each category, e.g. modPrintFunctions.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
