Thanks,
I haven't really done a lot of work with non-visual classes to this point. I wanted to throw this out there and see if anyone said "OMG, do it this way, because..." There seem to be tradeoffs either way.

I like how VCX files are organized. It's easier to pick a class and work with just that class. However, I also like the idea of everything being spelled out in text - like a class module in Visual Basic. But, of course, each class in Visual Basic is a separate file so you only ever have to work with the code for a single class at a time. I can do that in VFP, but would have use some construct like #INCLUDE to make it work.

Thanks for the info, guys.