>continued ...
>1. IMHO, the case that was made for RDBMS and the structured approach in the seventies was (and still is) far more convincing and consistent that the nebulous argumentation of OO.
>2. in OO circles, there is a doubt about the wisdom to implement OO in information processing systems as long as the database systems are not OO and even here there is discussion whether or not they will ever be!
while these may be true, they are not really important, in the sence that if you find something that works for you, and that your clients
find it OK as well, that your approach is valid, no matter what this
or that expert says.furthermore that fact that everybody says something
doesn't make it automatically right (the same goes for opting OO btw)

>3. as a VFP developer, you spend most of your time developing screens (and I understand that there are honorable exceptions to this, Arnon) and routines that are mostly not reusable because they are specific to the user domain.
the point is to build enough general porpose objects so that
they will be re-usable from project to project