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

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?


Use modules.

Make them Public and precede all macros in the module with

Option Private Module

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

"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

Hi Nick,

See the Run method in VBa help, e.g.:


Application.Run "'YourBook.xls'!Module2.ProtectBudgetSheetWithPass word"

Change Module2 to the name of the module of interest.


---
Regards,
Norman


"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

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

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