>while there are some problems with OO design and analysis in VFP
>(u might want to look in the lecture I'll publish on VFUG on this - hopefully it will be on-line by this saturday/sunday)

Can hardly wait until it will be available Arnon, by in the meantime, let me argue a bit with you.

It is not that there are problems with OO design and analysis here, in fact there is a major cath 22!. Either you build your systems OO or you do not. The benefits come from the incremental construction of a "framework" in function of which you can apply OOA and OOD, or am I missing something?

Now my point is this: information processing most of the application domain is contained in what is sometimes called persistent objects in OO terms. From what I understand, there is no such thing as a OODMS capable of saving persistent objects at this point in time, so you still have to save your 'objects' in a RDBMS, which is to date he most performant way of saving and retrieve large amounts of data.

... to be continued