Call is optional.
I prefer it because because:
a) It works in all versions, regardless of whether DoSomething is a Sub or
Function.
b) It standardizes the way arguments are passed (bracketing.)
c) It distinguishes a user-defined procedure from a built-in keyword.
which to me seems more consistent and readable (so maintainable.)
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"(PeteCresswell)" <x@y.Invalid> wrote in message
news:ob********************************@4ax.com...
Per Allen Browne:Then call it like this:
Call DoSomething(Me.[NameOfYourListBoxHere])
Any reason for using "Call..." instead of
DoSomething me.lstWhatever
?
--
PeteCresswell