>>>>All your forms should be based on the same form class. Data buffering, saving and un-doing changes, should be part of this class.
>>>
>>>How difficult is it to convert a form to use another base form?
>>
>>That would depend on how it is programmed. But it is worth-while to go ahead and base your forms on classes.
>
>I meant that we already have forms based on classes, but some are just based on the Foxpro base form. How difficult to change existing forms to be based off of a new form class instead of the default one?
Well, I think you could hack the form (i.e., open as table), and change the Class and Classloc fields or so. That part should be relatively simple.
However, you would then have to adapt your forms to the new way of doing things. This may take longer.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
