> When naming arguments for use in a sub or function, should I adhere to my
> usual naming format? E.G.
>
> Sub LOParas(ByRef rngWork As Range, strAction As String)
I think the ghoulash in arg names is ugly and redundant. Intellisense is there, to
tell you what type it is, so what's the point? Make it *functionally* meaningful,
and you'll be farther ahead.
> Sub LOParas(ByRef Range As Range, Action As String)
I wouldn't use keywords as argument/variable names.

Signature
.NET: It's About Trust!
http://vfred.mvps.org