If I remember correctly, my original post was looking for a way to build an object model, or a place to start. I got a few posts stating that it had to be broken into a simple question, but most of the posts discouraged me against a pure OOP model. I appreciate all the opinions, but I really need an answer rather than an opinion that does not deal with an answer. The answer does not have to be: I wouldn't do that. Whether it is practical or not, I can deal with. I appreciate your respone Al, I will get the book and read it thoroughly, I believe OOP is the way to go, IMHO and I will work hard to achieve results. I guess no one has attempted what I am attempting, going with objects that model all the actors in a system, if they had, they would have a good handle on what makes up a good business object model and how it can work with the system. Lets face it, relational database design has been beat out like a dirty carpet, but object modeling is still new. I don't expect this question to be answered, but : If I were to create a customer class, it would have properties, such as name, address, city, state, zip, phone (on a very simple level). It would also have methods, such as requesting a sale, paying on an account, Menachem Baziam says it well in VFP unleashed (chpts 27-31 I believe). He just doesn't go into detail, therefore I don't know how to implement the class, does the data go to the object, then to the table? These are the kinds of answers I am looking for. I will post the answers when I find them. Who knows, maybe I could even create a presentation to post to the VFUG?

Greg