>3. For code-centric classes, try using PRG's. They are alot easier to manage than code in VCX's. And, in these cases, you really don't take advantage of inheritance all that much anyway.

Of course, this is all just preference, but I completely disagree here. How are prg's easier to manage?

I only use prgs to hold class definitions when I have to for the following reasons:

1. Having a class in a vcx makes it clear without opening it that it is a class or group of classes. With a prg, you have to open and inspect it.

2. If you have a group of classes in a single prg, you can't see them from the project manager. With a vcx, you just expand the vcx to make the contained classes visible. You can also drag from the PM to a form or another library, or remove classes from the PM.

3. Two words: Class browser. Try that with a prg.

All in all, it doesn't make a huge difference, but in my eyes, this is at least vcx:3, prg:0.