tags:

views:

1083

answers:

3

In Excel VBA (2003), I've noticed that any Public or Friend Sub method in either a module or ThisWorkbook that doesn't have any arguments will show up as a Macro that can be run by the user. I.e. when the user goes to Tools --> Macro --> Macros... (or Alt+F8) the method will show up in the list that can be run.

For sanity's sake (organization, maintenance, etc) I do need to separate the code into modules. I'm hoping to find a non-hacky way to hide some methods from the user, but still allow them to be visible to other code modules. Note that all the code is contained within the same application, so no external code is called.

My current work-around is to use Functions that return a boolean instead of Subs, and just ignore the return value. eJames suggested the option of using an optional argument in the Sub, which will also hide the method from the list of macros.

Neither of these feel quite right, however, so any advice about how to structure a non-trivial Excel VBA application would be much appreciated.

+1  A: 

One solution is to give the method an Optional argument.

Public Sub myPublicSub(Optional dummy_var As Integer)
    ...
End Sub
e.James
Thanks, eJames. I had meant to mention that as an option in my question too. In my mind, that 'smells' even worse than turning the public Sub ino a function. :)
AR
Fair enough :)Anyway, Jason Z's answer is the correct one.
e.James
+8  A: 

Add the following to the top of your module:

Option Private Module

From MSDN:

When a module contains Option Private Module, the public parts, for example, variables, objects, and user-defined types declared at module level, are still available within the project containing the module, but they are not available to other applications or projects.

Jason Z
My sincerest apologies. Incorrect comment removed.
e.James
No prob. I appreciate the reversal of your vote. Removed incriminating evidence :)
Jason Z
And I thank you for that. At least I learned something about VBA in the process! : )
e.James
I had shield away from this at first because it can't be used in 'object' modules like ThisWorkbook or sheets... but that problem was me having methods where I shouldn't. Thanks for this.
AR
A: 

Just a small addendum to Jason Z's answer: methods hidden by Option Private Module are still visible if you use Application.Run() to invoke the method.

Ant