Hiding a VBA Code from other users.

shamala · February 16th, 2006, 12:51 AM

Hi All,

I have seen some macro run excel programs, where the users cannot see the VBA code. Even after opening the Visual basic editor and list of macros will not be visible when the user select run button of the macro.
How it is possible?

Please help me in creating a macro program like this. where i can hide my valuable code.

Thank you.

maccas · February 16th, 2006, 09:44 AM

Shamala,

This is really a two part question. Firstly, you can ensure that your subroutines do not show in the Macro Run dialog box by ensuring that each one requires a parameter to be passed to it. You can do this even whilst requiring an Optional parameter which then does not affect the calling of the Sub. The following code should demonstrate the point:

Code:

Sub Test()

    MsgBox "Hello"

End Sub

Sub Test2(Optional dummy As Byte)

    MsgBox "Hello2"

End Sub

To lock up the code so it can't be seen from the VBE requires you to do something else, you need to lock the project for viewing. To do this go to the VBE, select Tools -> VBAProject Properties ... from the menus (NB if you've changed the name of your project from the default of "VBAProject" to something else then the menu option will read (something else) Properties ...). This will bring up the project properties dialog box. Select the Protection tab, check the lock project for viewing checkbox, enter a password and click ok. If you save and re-open the file you will not be able to view any of the code without first entering the password.

It should be noted that whilst this password provides a level of deterant to viewing the code it is not totally secure. There are programs available for purchase that will crack the password in less than a second. If you really don't want people to steal your intellectual property then you are best off getting a copy of Visual Studio, writing your code in VB / C, compiling your code into a DLL and linking your Excel workbook to the DLL. Its a lot more work though!

Maccas

shamala · February 21st, 2006, 02:09 AM

Hi,
Thank you very much for the valuable information.

Pavesa · May 6th, 2011, 04:35 PM

There's a handy program called "Protect VBA Code" by

dombajsoft.com

that encrypts the password so people can't crack the password and see your vba.

Pavesa · May 6th, 2011, 06:04 PM

Otherwise, there is DataSafeXL that costs...

Shasur · May 15th, 2011, 04:00 AM

Quote:

Originally Posted by maccas

Shamala,

This is really a two part question. Firstly, you can ensure that your subroutines do not show in the Macro Run dialog box by ensuring that each one requires a parameter to be passed to it. You can do this even whilst requiring an Optional parameter which then does not affect the calling of the Sub. The following code should demonstrate the point:

Code:

Sub Test()
 
    MsgBox "Hello"
 
End Sub
 
Sub Test2(Optional dummy As Byte)
 
    MsgBox "Hello2"
 
End Sub

To lock up the code so it can't be seen from the VBE requires you to do something else, you need to lock the project for viewing. To do this go to the VBE, select Tools -> VBAProject Properties ... from the menus (NB if you've changed the name of your project from the default of "VBAProject" to something else then the menu option will read (something else) Properties ...). This will bring up the project properties dialog box. Select the Protection tab, check the lock project for viewing checkbox, enter a password and click ok. If you save and re-open the file you will not be able to view any of the code without first entering the password.

It should be noted that whilst this password provides a level of deterant to viewing the code it is not totally secure. There are programs available for purchase that will crack the password in less than a second. If you really don't want people to steal your intellectual property then you are best off getting a copy of Visual Studio, writing your code in VB / C, compiling your code into a DLL and linking your Excel workbook to the DLL. Its a lot more work though!

Maccas

In addition to Maccas's solution you can either do the following

1. Write the code in a function (instead of subroutines)

Private Function Test2
...

End Function
or

2. Set the access to Private.

Private Sub Test2

End Sub

Appreciate Maccas' detailed response

Cheers
Shasur