How do I organize MS Access functions and subroutines into standard modules?

Question

What are conventions for the grouping of subroutines and functions into standard modules with the MS Access VBE? I can find plenty of information on nomenclature and the function of subroutines and functions within modules, but nothing on how to group subroutines and functions into standard modules.

Currently, I have two total standard modules-- one called "Subs" and one called "Functions", each containing hundreds of lines of code that it is becoming a drag to navigate. What guidelines can I use to make it better?

Answer 1

Thanks so much for your feedback, @Mat's_Mug and @iDevlop. Your respective abstract explanation and more concrete response both moved me toward the answer I was looking for. It seems like both of you are suggesting, too, what my fruitless googling before asking this made me suspect, and what @Darren_Bartrup-Cook alluded to above-- there is no formal structure for organizing modules, and appropriate structure can very widely from one database to another. Correct me, please, if my takeaway is wrong, but what I've gleaned from what both of you have said is that the general principles to pursue are:

• to find groupings that are meaningful and useful within your own code (better to risk grouping too small than too big, maybe?)
• to keep implementations at a high level of abstraction, for the readability/ease of debugging the code