Hi Arnon,

>there is of course the posibility of wrapping every table by an object
>but u pay a speed penalty and increase the complexity of you program
>with out much gain
>what i do is take an OOPish approach in my design and analysis
>that is see the the objects as a whole (it is kind of a hybrid between traditional Anylisis/Design and OOAD) i think it is good (other may think
>it is not that brillient- e.g. Jose Luis Santaigo R <s>)

Is not that i don't like it. As you said having a pure
OO aproach may lead to serious performance drawbacks when
u try to access your data, among other things. There are
many debates about how to handle OO with relational
databases. Your's sound like a reasonable one, because,
AFAI understand it, the data model design is still based on a
relational aproach.

My point is: u can't forget about ER design as long as
u have to use a relational database, as VFP is, and a very
good one. The hibridity (this word i uglier than OOPish! :))
is of course necesary when u deal with an OO programing
language.

I can't say if it's brilliant right now, but maybe if there
is a VFUG lecture about Arnon's Relational Objects i'll read
it, and then give my final opinion about that! :)

Ciao!

J. Luis