I like Option Private Module. It's my current favorite.

"Bob Phillips" wrote in message
...
Tim,

It is not something I do often, but I have done it. I offered three
methods,
all have drawbacks.

The first is to make it Private. This may not be possible if called from
another module.

The second is to make it a function. This is both my least and my most
favourite approach. I tend to write more functions than subs, returning a
result, so my most favourite. But it will appear in the function wizard,
so
also my least favourite.

The third, by adding a parameter, than can be a do-nothing parameter,
means
that it does not appear in the macros, does not appear in function
wizard,
and does not affect the running. Making it optional means that no code
needs
to change. So a sub like

Public Sub TestSub(Optional dummy as Boolean)
...
End Sub

and just ignore dummy .

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"Tim Zych" wrote in message
...
Bob, why do you recommend adding a parameter simply to hide the macros
from
view? Is that something you would really implement?


"Bob Phillips" wrote in message
...
Either

make them Private
make them Functions (they will be visible from the function wizard)
make them public but pass a parameter

--

HTH

Bob Phillips
... looking out across Poole Harbour to the Purbecks
(remove nothere from the email address if mailing direct)

"gr8guy" wrote in message
...
Hi,

Is it possible to hide macros from a user so that they are not
visible
in
Tools Macro Macros & so that user may not run them by mistake?


Rgds,

Eijaz