I wasn't even thinking of creating a vcx, just a prg file. The original ideal came about from working with VB's template classes (which really isn't much).

Basically, I would create a simple dialog form (e.g. wizard) where a developer could specify the table, type of data access (i.e. VFP, ADO, SPT) and few additional options and the wizard would generate a 'skeleton' class definition file (prg) with generic data/class attributes like those I've mentioned.

Of course, the generated file would not be complete and will necessitate editing but I think it would cutdown unnecessary typing and/or copy/paste dramatically.

>>>Except the objects created with SCATTER NAME don't have a SaveAsClass method.
>>
>>How is this an issue when all of the behavior to be subclassed is in the wrapper object?
>
>I just don't think it tackles the question. The quest is a shortcut to creating table template classes, with methods for specific functionality for each field in the form of Access/Assign methods.
>
>There is no built in way in VFP to add custom methods programmatically. You'd have to hack the vcx.
>
>If you want to do this by hacking the vcx, you'll have add a line to the reserved3 field that looks like:
>
>*MyMethod
>
>and then add the method code to the Methods field, wrapped in a PROC/ENDPROC. Also, manually compiling the vcx wlil be necessary after you are finished modifying.