That's probably a fair assessment. I've never understood classes completely,
and therefore never use them and 'make due' with functions alone. A far cry
from the macro example I believe, but your point is well taken.

I would have to say it has more to do with style than anything else.

A program will function and maintain just as well with functions alone, or
classes and functions. Assuming both are well documented, and both use error
checking judiciously.


"Jamie Collins" wrote in message
ups.com...

Steve Schroeder wrote:
I use functions almost exclusively, data in, data out...comment my
code,
and use error checking judiciously.

If it gets any more complicated than that, it probably don't belong
in an
Office VBA app.

It's a paradigm shift: you don't get it 'til you get it. I bet there
are many out there who say, 'If the Macro Recorder can't record it, it
probably don't belong in a macro,' but they have to 'get' the fact that
Select'ing and Activate'ing isn't the best approach before they can
progress.

Jamie.

--