It doesn't really see them differently. You can't click on a macro that
requires an argument and hit run, which is pretty much wat the Alt+F8
approach is designed to do - so excel doesn't make them visible in the list.

--
Regards,
Tom Ogilvy

"Ladislav Ligart" wrote in message
om...
Follow up:

I found that if I removed the parameter passing, my wkbUtils.Runner
proc is called even with security on High:

fails .OnAction = "'wkbUtils.Runner " & """" & vProcs(i) & """"
& "'"
works .OnAction = "wkbUtils.Runner"

So it's the parameter that's messing things up.

Other tidbit:

With the parameter in Runner, "wkbUtils.Runner" doesn't show in
Alt+F8. But when I remove it, it does show:

no show Public Sub Runner(ProcToRun As String)
shows Public Sub Runner()

So it seems Excel views macros with parameters somehow differently.