>>The solutions to this that I saw were either on the most granular case (one per, good naming), or somewhere in between, with classes arranged into classlibs by theme. For instance, there were about 100 reporting classes, and these were grouped into about a dozen of classlibs by theme (sales reports, schedules, personnel reports etc), so when the time came to rework almost all of them, it could be done by several programmers at once, without stepping on each other's toes.
>
>I've actually come around to liking classes in program files as then you can use merge facilities in source control. Vcx classes are great in that you have the nice interface features and the fact that they are a table can be usefu but I have found that the document view is almost as good and text files are very flexible.

I've also gone back to prg files. My forms are in vcxes, but I'm loading a prg-based driver object in form's load, and that one contains all the code for the form. The form has almost no code at all, and the buttons etc only call driver's methods.

The last big scx I had taught me that it can become really messy really fast, with code spread all over the form. Sometimes it could take me minutes to find where exactly was the code I was looking for.