There should be no problem having Subs in a code module that you call from an activity module, as long as the view objects (buttons, labels, etc) "live" within the activity module and are declared there in Globals (ie, NOT in Process_Globals), and you pass them to the code module sub as parameters rather than (try) access them directly as globals. This doesn't make your activity code less long and confusing, but perhaps it might help by letting you group related code together
Backtracking slightly, though, if the issue is that your activity code is too long and confusing, remember that:
1/ you can use the outlining feature of the code editor to shrink Subs to a single line (or two) when you're not using them
1b/ eg, put cursor in activity module code, then: menu Edit, Outlining, Collapse All
1c/ and similarly, once you've recovered from the heart-attack induced by seeing all your code vanish: menu Edit, Outlining, Expand All
2/ subs are collapsible automatically, but you can also set up your own collapsible outline regions that encompass multiple subs, eg you could have regions for, say, initialization, event handling, activity/form handling, and helper functions, that would group similar functions together and hide them when you're editing other bits of the code.
2/ you can easily navigate between Subs (and modules) using the Modules tab of the Libraries/Logs/etc panel (usually the right-side of the IDE window)