>Marty,

>Another question ... what is the benefit to making these classes instead of just the ordinary old functions/procedures that we're all used to using? After all, I ended up putting them into a procedure library that's accessible from the entire project ... what's the diff? Enquiring minds want to know! < g >

Defining classes programatically (i.e. using DEFINE) is just like defingin the classes visuall - in fact if you view the code of your VCX (using the Class browser) you'd see the DEFINE CLASS syntax
The benfit of this over old function/procedures is the benfit of OOP vs procedual coding

As David said in most cases you can define classes visually which is more developer-friendly there are certain cases though when it is better to use a prg
for example classes VFP does not let you sub-class visually such as page,header,dataenvironment etc. or subclasses of ActiveX controls to prevent version problems

Arnon