Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I'm a bit confused: I want to put Option Private Module at the top of all
modules in my addin that contain UDFs because I don't want them appearing in the function wizard. However, is this going to affect my being able to access routines in my addin from elsewhere? VBA help says "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." I was worried this would stop me being able to use code like the following from other projects: Application.Run ("myAddin.xla!myMacro", arg1, arg2) This still appears to run fine, despite having Option Private Module at the top of the module containing myMacro. What then are the ramifications of putting Option Private Module at the top of every module in my addin? Am I going to have any problems with pre-existing code in other workbooks that refer to my addin code? |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Private Sub - Only Accessible from same Module? | Excel Discussion (Misc queries) | |||
Improve method of calling a private function in a private module | Excel Programming | |||
How to call a private sub() in another module | Excel Programming | |||
Option Private Module | Excel Programming | |||
Option Private Module not preventing cross project referencing | Excel Programming |