Home |
Search |
Today's Posts |
#6
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I think he is referring to something very basic, if they can't see them from
Excel, they won't touch them. -- HTH Bob Phillips (replace somewhere in email address with gmail if mailing direct) "Mike Fogleman" wrote in message ... Nick, I think you have the wrong idea what Private does. It does not prevent tampering in the VBEditor, it hides them from certain other macros. As you have just found out. Macros in a general code module usually are not private. To prevent code tampering, password protect the VBA Project. Mike F "Nick Smith" wrote in message ... Folks, just about finished this thing and am now making all the macros private to prevent tampering only to find that any private macros called within another macro cannot be found. I get a "Sub or Function Not Defined" compile error. Macro being called is "Private Sub ProtectBudgetSheetWithPassword" and the line Call ProtectBudgetSheetWithPassword fails. Any ideas? Thanks, Nick |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Calling Private Sub/Function | Excel Programming | |||
private macro and shortcut key | Excel Programming | |||
Calling a Private Sub | Excel Programming | |||
Calling a private sub | Excel Programming | |||
calling private subs | Excel Programming |