Does that make it any clearer?

Regards

Stephen Bullen
Take your Excel development to the highest levels
with "Professional Excel Development",
www.oaltd.co.uk/ProExcelDev

Think of a "Class" as a series of subroutines and functions that build a car
(kinda like a dll). The Functions return values for the characteristics (or
"adjectives") that describe the car (e.g. color, trim, interior). These are
called properties.

The subroutines cause the car to do certain things (Speed up, slow down,
stop). These are called methods.

Once you write the code, to slow down, for example:

Sub Slow_down(mph)
do until car.speed = mph
 apply brakes 'Which may be another "method"
loop
end sub

You never have to write this code again. Instead, you can simply invoke the
"Slow_down" method of the car class and pass it the desired speed.

Had I created a "Property" named "Speed" for the car, I could have set the
"property" with setProperty to the lower speed:

Function speed(mph)
set property  car.speed = mph
end function

Now I can create any number of cars (objects) with any number of
characteristics, and have them do any number of things, just by calling the
Dll (called "instantiating" or "creating an instance of") and passing in the
specific Function (setting the properties) or Subroutine (invoking the
methods) parameters rather than writing the code whatever number of times.

Clearly an "oversimplification" but, pretty much the basics of OOP. Program
the "object" car by setting its properties and invoking its methods, rather
than programming the computer to do these things

As one of us "old timers" surely you remember writing the BASIC code to
create a string of "-"s to form a line across the screen to create a display
box. Then counting pixels and spaces to fill the box with text. Well, now, we
only need to set the properties of the TextBox object and all that code
"happens" because somebody created a TextBox class of object..

Clearer?

BAC