I can just underline that. In one project we have about 200 VCX Files at the moment working with 5 developers.

I would strongly recommend to keep forms and Business Object stuff in differt libraries. Even if you get more libraries.

This will make life easier when you want to change the UI tier to e.g. .NET.
Because then you only need the BizObj libraries in the COM server.

Another tip: If we run into situations where more then one person needs to work on the same module we just extract classes from a lib (drag and drop in proj manager) and then put it back to the vcx when we are done. That works pertty fine because MM environment doesn't care about the library, as long as you don't do this with parent classes, that have inherited children.

Marcus


>In addition to what Marcus said, I'd also recommend splitting your class libraries up by function, rather than by type. For example, in the devguide, there's a recommendation to put the forms in the aforms library, biz objects in abizness, etc. This works fine for a single developer, but severely limits the ability to have different developers working on different functional areas simultaneously. There's no good way (that I know of, at any rate) to allow multiple developers to work on the same classlibrary, and then merge the work of the developers.
>
>In some cases, I've even considered (though have not yet done it) having a number of class libraries with one class.