Home |
Search |
Today's Posts |
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Hi all,
We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#2
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Why do you need to protect the workbook dynamically, why not just set the
password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#3
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Thx for the reply.
If the workbook is Protected in the design mode then I won't be able to open it in XLAM and work upon it i.e Paste Data and apply Report options, etc. The flow is that the user uploads the Template ( a simple workbook empty formulas and empty ranges where data would be pasted and formulas would calculate on the data pasted) which is opened in XLAM and worked upon and saved as the final report. So if the Template itself is protected then XLAM wont be able to open it and work upon. Please let me know if I am missing something. "Bob Phillips" wrote: Why do you need to protect the workbook dynamically, why not just set the password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#4
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
I think that you can, I certainly do that all of the time.
I have never had to unprotect my code to run it, worksheets yes, but not the code. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Thx for the reply. If the workbook is Protected in the design mode then I won't be able to open it in XLAM and work upon it i.e Paste Data and apply Report options, etc. The flow is that the user uploads the Template ( a simple workbook empty formulas and empty ranges where data would be pasted and formulas would calculate on the data pasted) which is opened in XLAM and worked upon and saved as the final report. So if the Template itself is protected then XLAM wont be able to open it and work upon. Please let me know if I am missing something. "Bob Phillips" wrote: Why do you need to protect the workbook dynamically, why not just set the password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#5
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Agreed. I don't have to unprotect the code to run it.
But then I have a "Delete macro" option, which user can select and I have to delete all the macro code from the XLAM and then save the Final Report workbook. I guess for that purpose I will have to unprotect the code too. Thx for the reply. "Bob Phillips" wrote: I think that you can, I certainly do that all of the time. I have never had to unprotect my code to run it, worksheets yes, but not the code. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Thx for the reply. If the workbook is Protected in the design mode then I won't be able to open it in XLAM and work upon it i.e Paste Data and apply Report options, etc. The flow is that the user uploads the Template ( a simple workbook empty formulas and empty ranges where data would be pasted and formulas would calculate on the data pasted) which is opened in XLAM and worked upon and saved as the final report. So if the Template itself is protected then XLAM wont be able to open it and work upon. Please let me know if I am missing something. "Bob Phillips" wrote: Why do you need to protect the workbook dynamically, why not just set the password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#6
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Then you are stuck, there is nothing exposed in the VBE object model to
allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Agreed. I don't have to unprotect the code to run it. But then I have a "Delete macro" option, which user can select and I have to delete all the macro code from the XLAM and then save the Final Report workbook. I guess for that purpose I will have to unprotect the code too. Thx for the reply. "Bob Phillips" wrote: I think that you can, I certainly do that all of the time. I have never had to unprotect my code to run it, worksheets yes, but not the code. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Thx for the reply. If the workbook is Protected in the design mode then I won't be able to open it in XLAM and work upon it i.e Paste Data and apply Report options, etc. The flow is that the user uploads the Template ( a simple workbook empty formulas and empty ranges where data would be pasted and formulas would calculate on the data pasted) which is opened in XLAM and worked upon and saved as the final report. So if the Template itself is protected then XLAM wont be able to open it and work upon. Please let me know if I am missing something. "Bob Phillips" wrote: Why do you need to protect the workbook dynamically, why not just set the password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#7
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
I know that. And that is why I was trying other approach (refere to the code
above). But somehow it doesn't work immediately after insert the macro in the workbook. I even tried Inserting Macro-Save workbook-Close Workbook-Open Workbook-Run Macro approach. It still fails. Not able to identify what is going wrong. Thanks for the help. "Bob Phillips" wrote: Then you are stuck, there is nothing exposed in the VBE object model to allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Agreed. I don't have to unprotect the code to run it. But then I have a "Delete macro" option, which user can select and I have to delete all the macro code from the XLAM and then save the Final Report workbook. I guess for that purpose I will have to unprotect the code too. Thx for the reply. "Bob Phillips" wrote: I think that you can, I certainly do that all of the time. I have never had to unprotect my code to run it, worksheets yes, but not the code. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Thx for the reply. If the workbook is Protected in the design mode then I won't be able to open it in XLAM and work upon it i.e Paste Data and apply Report options, etc. The flow is that the user uploads the Template ( a simple workbook empty formulas and empty ranges where data would be pasted and formulas would calculate on the data pasted) which is opened in XLAM and worked upon and saved as the final report. So if the Template itself is protected then XLAM wont be able to open it and work upon. Please let me know if I am missing something. "Bob Phillips" wrote: Why do you need to protect the workbook dynamically, why not just set the password in the design mode? -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Hi all, We are using Excel for reporting in our organization. Basically there is a Java web application which instantiates Excel 2007 with an XLAM. This XLAM opens a Report Template(an .xls, .xlsm file, name supplied as command line parameter). The Template has a data sheet where we have multiple ranges and the Report sheet which shows the final report based on the data from the DataSheet. The ReportSheet contains formulas to show the final output. It could contain Charts/Graphs also. The data is fetched from SQL server and is pasted on the Ranges. And finally when all the data is pasted and Macro is run the Template is saved as a Final Report somewhere on the Report Server. The Excel runs in the background in all this process. There could be multiple instances of Excel running on the same box. The instances run under separate WindowStation. In this process depending on the options selected by the end user, the Report options are applied on the final report workbook. The some of the Report options are Protect Workbook, Protect Worksheets, Protect Macro Code, Delete Macro code, etc. I am facing a problem when it comes to Protecting Macro Code. I believe that there is no API/Excel Object Mode available to accomplish this task. Given below is the code I am using for protecting the macro code. Sub protectMacroCode() With Application .CutCopyMode = False .DisplayAlerts = False .SendKeys "%{F11}", True .SendKeys "%T", True .SendKeys "E", True .SendKeys "^{TAB}", True .SendKeys "%V", True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "{TAB}" & Trim("XXXXXX"), True .SendKeys "~", True .SendKeys "%{F11}", True End With End Sub The XLAM writes the above code to the Report Workbook and Excutes this macro code. The macro is successfully written in the workbook but does not work as expected when call from XLAM. Whereas this particular piece of code works fine when the workbook has this macro already present and the XLAM just executes it. If anybody have any idea please let me know as it is a blocking issue in our process. Any help appreciated. Thanks in advance. |
#8
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
That is not designing around it as I see it, that is still trying to allow
dynamic code deletion. By designing around it, I mean add some logic so that the macro won't run in those circumstances, it will still be there, but dormant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... I know that. And that is why I was trying other approach (refere to the code above). But somehow it doesn't work immediately after insert the macro in the workbook. I even tried Inserting Macro-Save workbook-Close Workbook-Open Workbook-Run Macro approach. It still fails. Not able to identify what is going wrong. Thanks for the help. "Bob Phillips" wrote: Then you are stuck, there is nothing exposed in the VBE object model to allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob |
#9
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Sorry, but I am not sure I got you fully.
Thanks for the reply "Bob Phillips" wrote: That is not designing around it as I see it, that is still trying to allow dynamic code deletion. By designing around it, I mean add some logic so that the macro won't run in those circumstances, it will still be there, but dormant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... I know that. And that is why I was trying other approach (refere to the code above). But somehow it doesn't work immediately after insert the macro in the workbook. I even tried Inserting Macro-Save workbook-Close Workbook-Open Workbook-Run Macro approach. It still fails. Not able to identify what is going wrong. Thanks for the help. "Bob Phillips" wrote: Then you are stuck, there is nothing exposed in the VBE object model to allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob |
#10
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
As an example, I would have my macro test for a name constant in the target
workbook. If it does not exist, the default state, then I would run the macro. If it did exits, I would exit silently. Then, where you want to add code to delete that macro, I would set the name constant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Sorry, but I am not sure I got you fully. Thanks for the reply "Bob Phillips" wrote: That is not designing around it as I see it, that is still trying to allow dynamic code deletion. By designing around it, I mean add some logic so that the macro won't run in those circumstances, it will still be there, but dormant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... I know that. And that is why I was trying other approach (refere to the code above). But somehow it doesn't work immediately after insert the macro in the workbook. I even tried Inserting Macro-Save workbook-Close Workbook-Open Workbook-Run Macro approach. It still fails. Not able to identify what is going wrong. Thanks for the help. "Bob Phillips" wrote: Then you are stuck, there is nothing exposed in the VBE object model to allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob |
#11
Posted to microsoft.public.excel.programming
|
|||
|
|||
Protecting macro code programatically
Hi Bob,
Thanks for the response. Continuing our discussion with Protecting macro code programatically, I have been able do that programatically with SendKeys, but what I observed is that after Checking "Lock Project for viewing" and putting "Password to view project properties" when I close the workbook after saving it somehow Macro code is not password protected. I am doing all this operation from XLAM. I also observed that even after closing the workbook on which I worked on (password protect the macro code) I could see the VBAProject still open in the VB editor. And also I could see the protection in the VBA Project. But when I re-open the workbook, the macro code is not password protected. Any info on this would help me a lot as it is really a blocking issue. Thanks in advance. "Bob Phillips" wrote: As an example, I would have my macro test for a name constant in the target workbook. If it does not exist, the default state, then I would run the macro. If it did exits, I would exit silently. Then, where you want to add code to delete that macro, I would set the name constant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... Sorry, but I am not sure I got you fully. Thanks for the reply "Bob Phillips" wrote: That is not designing around it as I see it, that is still trying to allow dynamic code deletion. By designing around it, I mean add some logic so that the macro won't run in those circumstances, it will still be there, but dormant. -- __________________________________ HTH Bob "Anand Nichkaode" wrote in message ... I know that. And that is why I was trying other approach (refere to the code above). But somehow it doesn't work immediately after insert the macro in the workbook. I even tried Inserting Macro-Save workbook-Close Workbook-Open Workbook-Run Macro approach. It still fails. Not able to identify what is going wrong. Thanks for the help. "Bob Phillips" wrote: Then you are stuck, there is nothing exposed in the VBE object model to allow you to do what you want. Personally, I think that adding/deleting code/controls dynamically is not a good idea, it is better to design around it IMO. -- __________________________________ HTH Bob |
#12
Posted to microsoft.public.excel.programming
|
|||
|
|||
My solution
Hello there,
i coded a VBA module for Excel that allows to unprotect a VBA project programmatically. Nope, it does NOT break any password. That's, you need the password for the VBA project that you want to unprotect. It's just a different way than the SendKeys method. My method uses win32 messages and timers. HF ;) the link : http://www.twen.name/temp/jb_vbaproj...cker_v1.07.zip |
#13
Posted to microsoft.public.excel.programming
|
|||
|
|||
My solution
Very nice piece of work Jérôme! Thanks for donating it to us. It
definitely fills a need. -- Jim <gg67 gg67 wrote in message ... Hello there, i coded a VBA module for Excel that allows to unprotect a VBA project programmatically. Nope, it does NOT break any password. That's, you need the password for the VBA project that you want to unprotect. It's just a different way than the SendKeys method. My method uses win32 messages and timers. HF ;) the link : http://www.twen.name/temp/jb_vbaproj...cker_v1.07.zip |
#14
Posted to microsoft.public.excel.programming
|
|||
|
|||
My solution
Nice work :-)
But why place the code in "ThisWorkbook" ??? I took the liberty to move the unlocking code to a normal Module, and it works just as well - so, why place it in "ThisWorkbook"? PS: I also took the liberty to add support for Danish in 'Main Settings' as suggested :-) Keep up the great work, CE gg67 gg67 wrote: Hello there, i coded a VBA module for Excel that allows to unprotect a VBA project programmatically. Nope, it does NOT break any password. That's, you need the password for the VBA project that you want to unprotect. It's just a different way than the SendKeys method. My method uses win32 messages and timers. HF ;) the link : http://www.twen.name/temp/jb_vbaproj...cker_v1.07.zip |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Forum | |||
programatically deleted code still triggers macro warning | Excel Programming | |||
protecting macro code | Excel Programming | |||
Deleting macro code programatically | Excel Programming | |||
Hiding/Protecting the code of macro | Excel Programming | |||
protecting macro code | Excel Programming |