OO is not,as u said a panacea, but it does help to bridge the distance between analysis and code
Coad & Yourdon OOAD methodolegy (on which I base my approach)
is the closest to "old" E-R design while maintaing the benefiets of OO.
it is simple (some say too simple, I know) and it works form

Yourdon,btw speaks of OOAD for even non-OO tools like VB

IMHO by using OO approach in the analysis and design you gain a more complete view of the application at hand (as u see not only the data stucture) thus u have smotther move to OO coding, by OO coding you gain easier maintance better reusability rate (yes Lucienn <s>)

btw, Marc, in a sense VFP .dbc can be looked upon as a sort of a container object (not just because the initials) for the database
you have there the methods (a.k.a stored procedures) and the data (tables and properties of them like primery keys and relations)
but I am sure many ppl will disagree with this :)

>>
>>I defenetly agree that MMI design benefits the most form OO.
>MMI?
Man Machine Interface (GUIs are a ceratin kind of MMI)

ciao

Arnon