Creating COM Objects that read/write to Tables is one way to isolate UI and Data tiers...they are simple to make and use. I once wrote a set that could be called from VB or VFP. They did the reading/writing to the actual tables (DBC/DBF Tables).

HTH

-Irv.

>Hi
>
>I'm curious about using classes that (sort of) replace the need to directly communicate with tables.
>
>I understand there are probably a 100 designs to these objects, is there a standard to how they should function?
>
>I'm thinking along the lines of having a class that holds the Table name and contains familiar methods such as Save(), Insert(), Delete() etc. and having the Parent (form?) calling these methods rather than issuing updates directly.
>
>Then, rather than having global procedures/methods, have these methods sit in the data-object.
>
>Any guidance or links on this subject?
>
>Thanks
>Kev