>So far on this ‘mailing list/BBS’ and others no one has shown me a good reason not to split the classes into many VCX, and in fact given several good reason why it should be done, especially when dealing with multi-developers.
>
>So looks like that will be the avenue we will travel, assuming the development manager OKs it.

The only exception to this one-class-one-lib scheme would be if your form class has some control (which is a class of its own) which is very unlikely to be used anywhere else; then it makes sense to put it into the same classlib.

A half-way approach that I've seen was grouping similar forms into the same classlib. That was limited to the small forms used to enter selection criteria for reporting, so one group of reports would have all of its forms in one VCX. And then when there was something to do with these forms, it was quite often to be done on the whole series, and then one developer gets to do the whole group.

The corollary to this is: it's OK to group them into one classlib if you're sure you won't ever need two guys working on that group at the same time.