You are currently viewing the Word VBA section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Hi
Sorry for being late.
How reliable this method is? what's the probablity that this lock is broken?
and another question:
I've heard about a tool that make the code unreadable. for example it change the variable name 'Title' to 'HVKBmasc_sadc_vsac_sdac' or something longer that cannot be read. what are the name of these tools and how much do you know about them?
Thanks
If you are really concerned about the code safety, then you can try for some compiled solutions. VBA code even though protected can be easily broken by external tools.
Try for creating some DLLs that are really safe and then you can use them in your VBA
All you will be doing is write the business logic in class library project adn compile them as a DLLs then use it in VBA project
Hi
1- Adding dll file is done this way? Tools->References->Browse
2- Is dll file embeded in doc file?
3- How can I compile a VBA file to dll file? I don't have VB 6 installed on my machine.
Thanks