I am looking at VB6 code and I see a statement as follows -
Public Sub CheckXYZ(abc As Integer)
If abc <> pqr Then SetVars abc
<
I don't personally use or recommend the use of the Call statement. I find personally that the parens with functions and lack thereof with subs differentiate the two effectively. That said, I really like Matt's use of the call statement/byval/double parens. In the rare circumstances when you want this, it makes it stand out even MORE from every other call if it's the only place where you use the Call statement. I'm gonna use that, if I live long enough to need to. :)