>>Actually, I agree with you, but I'd like to play devil's advocate. What about those that say that OO is a tool just as everything else. It is to be used, but it is not an End-all, Be-all. There are some problems that don't lend themselves easily to an OO solution. In some rare occasions a PRG would actually be more effective.
>
>Dan,
>
>I have heard that argument, but, interestingly, no one who made it ever gave me a situation where it was true. The only time I have found it helpful to use a proc is when the routine is simply an extension of the language.

Brief input:

When I first started using VFP I went through the process of questioning my roots in procedural programming. I also felt a little claustrophobic inside the Visual GUI, wondering 'where's the code?'. I am now in the process of transforming all my prgs into custom class method code. I can use the class anytime anywhere just by creating the object when I set my environment in the application object of my framework. I have direct access to all the code that was previously stored in a directory full of .prg files. Very clean and easy.
I wouldn't even consider creating classes using a .prg file. Why?