> Hi,
I looked at the StackOverflow answer regarding regions, and while I get what it's trying to say about splitting a class into smaller classes as a class is doing too much, I don't feel like that's always applicable. In the project I'm working on right now, I've got about 15 properties for a class, which, because VBA has a very verbose implementation of properties, is overwhelming the number of subs/functions I have in my class, and the pieces are all directly related to the class they're