Declarations and Procedures in Class Modules vs. Dependencies

[cafeenman]

I keep reading that Class Modules should be self-supporting. That makes sense but it also means when you have, like in my app, over 100 class modules and they're all using bits and pieces of different .bas modules such as sorting arrays, API declarations and whatever else.

Is it best practice to copy and paste all of that into each class that uses them?

These dependencies are all over the place so making a dll isn't really a good option.

The only time it's really a problem is when I post code here and have to scamper all over my project finding all the dependencies so anyone else can try to use it.

For myself it's kind of a pain when I pull something into a new project but usually it only takes about 10 minutes to get it all sorted out by starting the project which then asks me what's going on with that thing that's not there and I go find it and pull it into the project too.

But let's say this was pro-development.

What is best practice?