>This is kind of a beginner (easy?) question. I've been learning VFP this last month at a new job, coming from C++ background. I can see why classes in C++, but why classes in VFP.

For all the same reasons.

>Perhaps we just aren't taking advantage of classes at work properly. Right now, I make a form into a class. Well why make a form into a class, when I can just keept he form as a form. Besides Heirarchy order (Having a classlib with classes in it, as an ordering device)...i'm just having a hard time figuring out what the use is...

OOP is OOP is OOP. *s*

There is a whole set of subclassed controls that you can use as _your_ baseclass. But, since you understand classes in C++ I know I'm telling you things you already probably well know.

An example of using them: You can map any subclass to any sort of control. So if your company uses a particular font for textboxes, map your class to the control and when you drop it on a form you get your standars.