Rina:

The 'Fields as Object Properties' scheme is useful when you may want to port to another Database besides native Fox (like SQL, Oracle, etc.) This is because there is no Table data-binding with Form controls. They are bound to the Object properties instead. It then becomes easier to replace just the Data Object layer and leave the visual Form layer relatively unchanged.

Actually, modifying the custom class for structure changes is not so hard, because you create Object properties with the same name as the Table fields using Afields() within a loop; this immediately detects any changes. You can also use Scatter/Gather oNAME as Cetin described.

I've never tried Memo fields, General fields, etc., and as he said there may be problems with field type support.

Just some thoughts,