> >Actually vcx's are class libararies that store classes. And classes are a > must if you do OOP. In VFP you should subclass the base classes of > everything and then subclass those for each application for a start. Read > Arnon's article on OOP in the VFUG newsletter section. > > SO OOP is like clicking on a gif in netscape that points to > something further? Is that what it can be compared to? no that is hyper-linking OO means that when you look on something you don't seperate it into data and procedure you look at it as a whole (as an object) you have classes which are abstract representation of object groups and each class has states and operations for example a pen can be considered an object - it has states e.g. full of ink or empty and it has operations like writing and chanign fill now there are 3 basic issues that makes a language OO encapsulation - information hiding , basicallly each class should hide at least one concept from the rest of the "world" and this gives yo a kind f black box approach to object - once you have them debugged you don't have to worry about what's goig inside the there inheritance - you can create new classes which are based on the classes you already made the new classes will inherit the charetaristics of your parent classes - you will only have to overwrite the things wich are diffent e.g. from the pen class we can create subclasses for fountain pens which still serves the same functionality but has some different properties another aspect of OO is polymorphism that is oneentity can have many forms this lets you call methods with the same name in different objects and the object will know what to do if we haev a shape class from which we craeated a circle sub-class and a rectangle subclass we can call the draw method of both objects (I consider an object an instantiation of the class) and each will do thier specific task this is only a very basic explanation of the basic OO charectaristics you should probably read some more on O in general and on OO in VFP Arnon