>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.
>
>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...
>
>thanks for the newbie help.
>
>matt
Converting a form to a class just for the fun of it is indeed pointless. But as soon as you have two similar forms, subclassing makes a lot of sense: most changes have to be done only once. Example: there are lots of similarities between "reception of articles" and "article delivery" (or sales), but I still want separate forms.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
