>
>I am not going to convert you (I guess),I think it helped
>me increase re-usability
>I don't build object-wrapper for every table, if that what you're talking about. but i use OO for building my DataEnvironments,forms,menus hopefully soon reports. I have built several components that I use and re-use repeatedly all over my application(s) - so I can say that OO works for me - me being the operative word here,
>if something else works better for you, use it ,you have to
>feel comfortable with the way you program, or you will indeed waste your time

Sure! But if you take such a conciliatory tone, there is no
discussion possible, is there?

I started this thread, because I've seen a lot of people
wondering how to go about and implement OO into their programs.
To be totally honest, I felt somewhat uneasy myself. So I
started to read. And what do I see: not much more than band-
wagon effect. Repetition of old recipees of project manage-
ment into a newish, AIish terminology. As though before OO we
did not reuse! As if prototyping and RAD are OO.

Where OO does make a difference is in real time applications,
or system software (GUI development for example). There
classes are indeed reusable and you can get leverage from
polymorfism and inheritance. And OO lies as the core of
your approach. But in information processing?

But you know all that do you not?

Regards,

Marc