Quote Originally Posted by Krool View Post
I just want to put out a question in the room.
Shall my new VBFlexGrid (almost completed) be included in this project or separated as initially intended to be?
Reason for my struggle is that it would fit perfectly in the architecture of this project, but did it separate because of the size and complexity.
However, who cares if the VBCCR15.OCX will be 4.4 MB or 5.6 MB?
Thanks
My first thought is that it's better to have everything in a single file.

Let's try to find the pros and cons:

Pros:
1) Everything in a single file/reference, is simpler.
2) Easier to find for people that don't know that it is available out there.
3) The file size is not a problem nowadays (at least in most of cases, perhaps 99%).

Cons:
1) To have everything together increase the number of types available. I mean, for example, one reason I don't like to use ADO is because I'm used to declare String variables as Dim a as str[and press Space or Enter] and it becomes Dim a as String, but having a reference to ADO it becomes Dim a as Stream, and I need to navigate down for several types to find String.
The point is that having unused Types is not good for intellisense.

Others?