Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel,microsoft.public.excel.programming,microsoft.public.office.developer.vba
|
|||
|
|||
![]()
Hi!
I developped some Excel XP macros in vbscript. Now it's time to deploy them to a unique client (only one computer). Those macros are made to be executed in many excel files, then for maintenance purpose it would be nice not to repeat those macros in each file. What are the possibilities to deploy my macros (compilation, template,...)? Also, i would like to protect my code. Depend on the deployment scenario, what are the possibilities? Thanks, Thierry Paradis. |
#2
![]()
Posted to microsoft.public.excel,microsoft.public.excel.programming,microsoft.public.office.developer.vba
|
|||
|
|||
![]()
1.st, you can compilate all your macros in a single Excel file and than
save the file as *.xla, than in the new PC you jast have to run the XLA file. 2.nd, to protect your code, you have to go to the VBA window (Alt + F11) and in the menu go to - Tools - VBAProject Properties... - Protection - here you can look the project for viewing and put a password. |
#3
![]()
Posted to microsoft.public.excel,microsoft.public.excel.programming,microsoft.public.office.developer.vba
|
|||
|
|||
![]() "Antunes" wrote in message ups.com... 1.st, you can compilate all your macros in a single Excel file and than save the file as *.xla, than in the new PC you jast have to run the XLA file. 2.nd, to protect your code, you have to go to the VBA window (Alt + F11) and in the menu go to - Tools - VBAProject Properties... - Protection - here you can look the project for viewing and put a password. Regarding that 2nd item, be aware that there are VBA password crackers that will break the code protection on an XLA in no time. Don't use this method if you want to ensure that your source code is protected against anything more than casual snooping. The only way to thoroughly protect the code is to move it out of VBA and into a language where the code can be compiled directly. A VB6 ActiveX DLL whose functions are called from a bit of stub code remaining in the XLA file would do nicely. -- Regards Jonathan West - Word MVP www.intelligentdocuments.co.uk Please reply to the newsgroup Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org |
#4
![]()
Posted to microsoft.public.excel,microsoft.public.excel.programming,microsoft.public.office.developer.vba
|
|||
|
|||
![]()
Instead of compiling the code, consider using Invisible Basic, a source
code obfuscation utility for Excel/VBA which can be freely downloaded at http://invisiblebasic.sourceforge.net Although they can still crack your password, after saving your workbook via Invisible Basic's "Save Invisibly As" command, the VBA code anyone will see upon cracking your password will be quite unreadable with comments removed, names scrambled, etc (though it will be functionally equivalant). John |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
how to deploy an Excel workbook office 2007 project? | Excel Discussion (Misc queries) | |||
How to deploy an Excel 2003 solution | Excel Discussion (Misc queries) | |||
Deploy Excel similar to Access Runtime | Excel Programming | |||
What's the best way to deploy a VB business logic with Excel? | Excel Programming | |||
Deploy Excel 2002 add-in | Excel Programming |