>>Why use classes? Procedural code gets the job done, right?
>
>Classes are for when there's data that must travel with the code. No point using a class for a bunch of functions that don't share data.
>
>Tamar

I've you're talking about VFP classes, OK. If you mean classes in general and the foundations of OOP, that's a different story and I would disagree. They can work with the implementation of interfaces. If that last statement you made were true across all of OOP arenas, then certain frameworks would really never exist. :)

VFP only implements a portion of OOP. Yes, other languages/products that claim to be OOP might not be so 100%, but VFP is comparatively further from the definition.