>>BTW, VFP is NOT pure OOP. There are a number of variations from the OOP theory that VFP has taken. So to design a 'pure' OOP app may be out of the question.
>>
>>Tom
>
>I'm not looking for a pure OOP design, but rather a starting place. C'mon, if we're going to model the business application to an object model, don't we have to start somewhere? I know we can start with a class that resembles an entity in the business application and add methods and properties to that entity, whether or not it is feasible or practicle depends on the outcome of the model. I stick with my prev response, thanks for the help, though.
>
>Gonna milk this OOP thing for all its got,

Greg

In true OOP design the data is integrated into the object. This is where VFP takes liberties. Another theory is that a UI is an object & data is an object. The more each object can stand on it's own -- or the more each is independent of the other -- the better the results. If this is true then your starting place does not matter because each is a seperate entity. So like I said earlier, whatever works bets for *you*. Especially since you are the one who will either be a star or a bum.... (s)


BTW, I like this line you wrote:

>>I know we can start with a class that resembles an entity in the business application and add methods and properties to that entity, whether or not it is feasible or practicle depends on the outcome of the model.

Kinda goes with what I said, you will either be a star or a bum.... (g)

Tom