VFP is supposed to be an OOP tool, how do we get to that point. I never before worried about creating a customer class. I would just create forms and put text boxes on the form, nav buttons, and so on. This is not the Object Oriented way. In an OOP system, there are classes that resemble real life entities, or is there?

my "philisophy" is that VFP is a mixed approach tool u have a fully qualified OO language and a real good RDBMS
so I take an integrated approach in OOAD - designing objects (keeping in mind that the data will end in tables), and trying to make it map ok both ways

so if I'll take your "customers" class in the diagram (created in the OOAD)
I have a representation of the customer object - this way I know what method and what properties(in this sense a propery can be a widget on the form) will be represented on the form
also note that all the widgets are designed and wrtten in OO manner

u can build wrapper object for each table and have a pure OO system
but IMHO it is a lot of work and the benfiets you'll get are not worth it