I'm tryin' to keep it short...

Holy criminy! (and thanks to Hutch for beating you to the punch)
... Your last comment is what would have answered my original Q.. (:-)


> > I still have problems telling a parameter from a method as well
as which methods apply to which objects.

Unfortunately, not knowing my knowledge, you spent most of your time
on things I know. Sub vs. function and passing parameters to/from
subs.

I was referring to VBA objects and the "after-the-dot" thingys. As I
think you said, these are not identified - as a method or parameter -
in the Intellisense "pop-up-after-the-dot-menu", and more
importantly, whether they actually are supported by *that* specific
object. What was initially misleading was the fact the the objects
the programmer forms *are* in that pop-up list, implying (or rather I
was inferring) it includes *supported* methods/parameters.
In my mind a parameter is some "characteristic" of the object and a
method is some operation  that the object supports/performs (code it
has and runs)
Some are obvious, like the color of something probably would be
considered by all as a parameter. This is all foggy and open to
intrepretation, of course.


> The term "method" is an object-oriented term and signifies the
method with which you communicate with the object.

communicate makes some sense, though I think of it (from some very
minimal coaching on OO concepts) as some operation that the object
has to / can perform rather than you having to perform it or asking
about some characteristic.



> Re which methods apply to which objects. There is nothing to
assist you here (except for the excellent help you get from Excel
when you type the dot).

There is the "Help" help, which ain't so bad some of the time,
but it uses uSoft terminology and if you don't know all the
terminology, Help it "aint". The concept usually is within
understanding except the terminology interferes with the message.




> As you write more and more VBA code, some of the constructs will
stick in your mind, ...

Naturally.



>... I had a fair bit of trouble, despite many years of using OO
languages.

My trouble was not 'hampered' by that type of unfortunate
experience. (:-)



[... snippitty...snippitty...snip...]

> Possibly the easiest attribute to check is Count. It will tell you
how many cells  are selected.

How I missed that as a possible solution when I carefully (yea,
right) tried all the "after-the-dot-thingys" that appeared and looked
like possibilities, but there it was, last night (in 97) when I
looked ... and the code is already changed... I just "knew" there
was a built-in function(sic) for that; it seemed like a natural.

The By Val / By Ref explanations given for VBA work for me, but I
rarely use that aspect. Weird or not I have 99% Public variables.
That way I never have to remember what I called something, and I
think my application (not to mention brain) fits that paradigm well
(don't need a lot of multi purpose subs). Whatever "floats your
boat", eh? You software geeks think differently and that's OK.