Encapsulation Best Practices

[pflugs30]

I'd like to hear from other contributors what they have done with VBA projects that grow quite large. I maintain an Access front-end database project that currently has over 175 modules, and I'm planning to create even more. RD takes over 15 seconds to parse all code files and tests, even after turning off unneeded capabilities. Plus, it's just a lot to look through, even with the folder structure in place.

I've experimented a bit with moving similar modules together into separate files and then referencing them from the main project. I liked how this felt like refactoring C# code into different class libraries and DLLs. I don't know how it would work for deployments, though. Additionally, I quickly found that the scope of 2 - PublicNotCreatable meant that I would have to create public Factory classes. Doable, certainly, but a code change.

What have others done? Should I consider moving modules to separate Access files? Should I move them to VB6 or VB.NET w/COM interop? Worth noting: I'm planning to rewrite the entire application as a modern web application within 12 months, so I don't want to completely redo everything. I'm trying to maintain for the time being.

Thanks for the input!