Fernando,

First my rule of thumb about procedures versus classes is if the routine is an extension of the underlying langauge then it is a procedure otherwise it is in a class.

As for why so many of the utility classes here are covering weaknesses or missing aspects in VFP it is because there are weaknesses and missing aspects in VFP. Creating a class is a way to distribute the neet way I got around one of those. Makling it a class makes it usable by those who are fully OOPified and those who aren;t can open the code and copy what they want out to their procedure file.

I would guess that 99.5% of my code is in classes and 0.5% is in proc files. Why, because OOP gives me a lot of advantages over procedure files in extending what I already have. In OOP I can subclass and extend instead of copying code into a new procedure and extending that (which now gives me two places to maintain the same lines of code). So one of the major advantages of using OOP today is what comes tomorrow not what I have today.