Place the bulk of any such code in a standard module and call on it from the worksheet. Include only minimal code in the worksheets.Review > Protect Workbook > to prevent worksheet copying. It is compatible with Microsoft Excel and Word files. Maximum 80 dummy modules are added in the VBA project during protection when binary format option are selected (most secure) to make it more difficult to crack.
The workaround for this problem involves 2 steps:įile > Info > Protect Workbook > Protect Workbook Structure or This small application can make the VBA modules and projects unviewable. Thus, the code embedded in the newly copied worksheet will be visible, even if the source VBA project was password locked or custom protected as unviewable or Unviewable+! Unfortunately, the properties of the source VBA project, including its password, cannot be transferred to the target workbook. The new workbook has its own VBA project, which is unlocked at the time of creation. Copy the worksheet with the event code to a new workbook.Lock the VBA project with a password (VBE > Tools > VBAProject Properties > Protection).Thanks very much for your help.VBA code stored in worksheets (document modules) can be read from workbooks with unprotected structure (Review > Protect Workbook), even if the VBA project is password locked or unviewable. This hack can be demonstrated with the following simple steps:
This is an excellent sample, and really shows off the power of accessing the salesforce api through the office toolkit, as well as some nice excel manipulations, etc. I just wanted to look under the covers a little more. I can still call the methods from either of those addins without having access to the source, so that is ok.
We will also show you how you may be able to gain access to the VBA code inside the locked project. This article presents the 2 main reasons behind this message. which I have now done after looking at the source code for the excel connector sample. While in Visual Basic Editor (VBE), you click on a VBA project and receive the ‘ Project is unviewable ‘ error, instead of a password input prompt. But now I understand that since I can't modify the source for either of those addins (sforce.dot or sfdc.xla), I need to create a new addin from scratch with it's own menus etc. Initiallly I thought I could/would just "extend" that addin to add a new menu item specific to my application (so i wouldn't have to recreate login dialog boxes and other things already in the menu). In my initial post, I was actually referring to the actual office toolkit plugin (sforce.dot) that gets installed when you install the salesforce office edition (not the toolkit used to develop custom addins, but the actual addin that allowed you to connect to salesforce from within word or excel). Thanks for clarifying the excel addin was password protected.
0 kommentar(er)
