Hi All,

(I'm not a VBA pro, more of an enhusiastic amateur)


Is it possible to better protect a VBA project?

I wrote a simple trading sheet for a guy recently
and I put a bit of code in to disable the sheet after
a day or two until he paid me.

What he did though was ask about on a few forums
and got info on how to easily crack a VBA project security.

I tried it and it was alarmingy easy.

He got hold of a Hex editor and created a VBA project with
an easily recognisable password, say DOGBONE for example.

He then found where excel stored this password via the
hex editor, opened my sheet and with the hex editor replaced
my password with the simple one.

Lo and behold he had cracked my VBA project security in about
5 minutes.

Is there a better more secure way to protect a VBA project?


Ron

Hi Ron,

I understand your concern about protecting your VBA project. There are a few steps you can take to make it more secure.

1. Password protect your VBA project: You can password protect your VBA project by going to the VBA editor, clicking on "Tools" and then "VBAProject Properties". In the "Protection" tab, check the "Lock project for viewing" box and enter a password. This will prevent anyone from viewing or modifying your code without the password.
   
2. Use a digital signatu You can sign your VBA project with a digital signature to ensure that it has not been tampered with. To do this, go to the VBA editor, click on "Tools" and then "Digital Signature". Follow the prompts to create and apply a digital signature to your project.
   
3. Convert your VBA code to an add-in: You can convert your VBA code to an add-in, which is a separate file that can be loaded into Excel. This will prevent anyone from accessing your code directly. To do this, go to the VBA editor, click on "File" and then "Export File". Choose "Microsoft Excel Add-In" as the file type and save the file.
   
4. Use third-party softwa There are third-party software programs available that can provide additional security for your VBA project. These programs can encrypt your code, add password protection, and more. Some popular options include VbaCompiler for Excel and XLS Padlock.

I hope these tips help you better protect your VBA project. Let me know if you have any questions or need further assistance.

Hi Ron,

Is there a better more secure way to protect a VBA project?

Yes there is (misplaced the link to this one):

1. Save the Excel workbook (.xls) file into an add-in (File SaveAs.....)
2. After you have the saved add-in (.xla), close the Excel workbook (.xls)
3. Double click on the add-in to open it
4. Press Alt+F11 to access the add-in's vba project
5. Lock the vba-project with a password
6. Double-click on the "ThisWorkbook" code module
7. Press F4 to open the Properties window
8. Change the "IsAddin" status to FALSE
9. Return to Excel by Pressing Alt+Q (or close the vbe window)
10. Go to Tools Share Workbook
11. When the dialogue appears, check the box for: (Allow changes by.....)
12. Press OK to close the Dialogue
13. When prompted to save, Press OK
14. Press Ok to accept that "macros cannot be accessed"
15. You should feel giddy at this point because you just realized what you have
been missing right under your nose
16. Verify that the [SHARED] appears in the application title bar
17. Now save the workbook again as an Add-in (File SaveAs...) overwriting the
previous one
18. Close this Excel workbook without saving the changes (you don't need it)
19. Test out your newly saved add-in (open it, access the vbe, try to expand
the project window, you should get the new message "Project is Unviewable"
20. Your done

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

Thanks,

It never ceases to amaze me how many good people are hanging around this
place with rapid response answers.

Thanks again, I will try it out.

Ron

On Jan 17, 5:50*pm, Jan Karel Pieterse
wrote:
Hi Ron,

Is there a better more secure way toprotectaVBAproject?

Yes there is (misplaced the link to this one):
....
10. Go to Tools Share Workbook
....
14. Press Ok to accept that "macros cannot be accessed"
Regards,

Jan Karel Pieterse
Excel MVPhttp://www.jkp-ads.com

Jan, my spreadsheet uses XML data, so when I follow this procedure I
get an error at step 10 saying "This workbook cannot be shared because
it contains Excel tables or XML maps...". Is there any way of
protecting my VBA?

Hi Brendanh,

Jan, my spreadsheet uses XML data, so when I follow this procedure I
get an error at step 10 saying "This workbook cannot be shared because
it contains Excel tables or XML maps...". Is there any way of
protecting my VBA?

Looks like you can't, I'm sorry!

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

I got this to work once. Later when I updated the file, I got a message that
this was not a valid add-in? Thoughts? Thanks!

Hi Karel

Does it works also with office 2010,
becouse I follow all the steps but it does't work :-(

Thank you in advanced
Carlo

I can't get it to work with Excel 2007 or 2013 either. I wonder if there was a patch in the last round of MS Office Updates?

Hi Karel

Does it works also with office 2010,
becouse I follow all the steps but it does't work :-(

Thank you in advanced
Carlo

Best solution for the buck, IMO, I've ever found...

http://dombajsoft.com/protectvba.htm

...where it generates a protected copy for distributing and lets you
work with the original version in the normal fashion!

Displays "Project is unviewable" same as JKP's solution does, but not
'undoable' like JKP's is.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Unfortunately, I'll have to wait until I get home to look at it. My Work blocked that page.

However, using the code equivalent of JKP's solution I was able to get it to work (on 2007, haven't tried 2013):

Workbooks("test.xla").SaveAs "c:\test.xla", AccessMode:=xlShared

Unfortunately, I'll have to wait until I get home to look at it. My
Work blocked that page.

However, using the code equivalent of JKP's solution I was able to
get it to work (on 2007, haven't tried 2013):

Workbooks("test.xla").SaveAs "c:\test.xla", AccessMode:=xlShared

And so is undoable, allowing 'savy' users to 'break in'. The solution I
use requires binary editing of the file for do/undo and so not so easy
to 'break in' for most. Also lets me use 'version stamping' on the fly
so my install knows when it's upgrading vs updating apps that require a
license.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Unviewable+ VBA Projects for Excel & Powerpoint

http://spreadsheet1.com/unviewable-v...for-excel.html

An Unviewable VBA project cannot be defeated by numerous password hacking software, such as this password recovery add-in. The unviewable plus VBA application is NOT based on the old shared workbook trick, which is easy to overcome and cannot be created, if there are Tables in your workbook or add-in.

The software is an executable that will turn your add-in (or workbook) into an add-in (or workbook) with an unviewable VBA project. Besides Excel macro-enabled files, the unviewable+ application can also protect PowerPoint presentations.

This does same for all MS Office apps and most others that license VBA.
It only costs $20...

http://dombajsoft.com/protectvba.htm

...and hasn't been broken yet (AFAIK)!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Voucher Lazada Voucher [/color]Lazada, Zalora 2 triệu VND, mã giảm giá, phiếu giảm giá, voucher giảm giá Lazada, Zalora với số lượng lớn, duy nhất chỉ có tại BizzaViet. Đy là ...

Buy/Download links seem broken or non-valid anymore from my end. It looks like an abandoned project.

Not every VBA projects that is reported as unviewable in VBE is created equal. Unviewable+ packs more tricks behind the hood. Read mo

http://spreadsheet1.com/unviewable-v...for-excel.html


On Friday, April 17, 2015 at 3:06:44 AM UTC+8, GS wrote:
This does same for all MS Office apps and most others that license VBA.
It only costs $20...

http://dombajsoft.com/protectvba.htm

..and hasn't been broken yet (AFAIK)!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Buy/Download links seem broken or non-valid anymore from my end. It
looks like an abandoned project.

Hmm.., you appear to be correct. I don't know the status of the product
as I've been using it for some years and so not keeping track. I'm sure
contacting them will fix the situation!


Not every VBA projects that is reported as unviewable in VBE is
created equal. Unviewable+ packs more tricks behind the hood. Read
mo

Yes, I know this! I read extensively about Unviewable+ after a
recommendation by Chris Newman. It appears to modify the binary in the
same way PVC does, to render VBA projects unviewable!

http://spreadsheet1.com/unviewable-v...for-excel.html


On Friday, April 17, 2015 at 3:06:44 AM UTC+8, GS wrote:
This does same for all MS Office apps and most others that license
VBA. It only costs $20...

http://dombajsoft.com/protectvba.htm

..and hasn't been broken yet (AFAIK)!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

PVC should be identical to Unviewable+ SIMPLE protection level. I believe that's where the similarities end. Certainly, it was a great program when it was first launched many years ago. Hacking methods have become more sophisticated since then, hence the need for a stronger protection.

Yes, I know this! I read extensively about Unviewable+ after a
recommendation by Chris Newman. It appears to modify the binary in the
same way PVC does, to render VBA projects unviewable!

hi,

I have tried JKP process and it works but my file contains web quires and when try to run it shows runtime error 1004 is there any solution for this?

regards,

Prashant

hi,

I have tried JKP process and it works but my file contains web quires
and when try to run it shows runtime error 1004 is there any
solution for this?

regards,

Prashant

Unviewable+
It's not free!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

No cases that I'm aware of!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:
GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

No cases that I'm aware of!



Thanks
I will try it.
I do no need anything more just VBA protection.

GS wrote:
GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

No cases that I'm aware of!



Thanks
I will try it.
I do no need anything more just VBA protection.

It doesn't do anything else. It renders the same 'effect' as JKP's
shared workbook trick, (which as you probably know can be undone) by
altering the binary at various levels. Only admitted flaw to date is
that if you use the 'optional' advanced protection it loses a level
when you save your file. IMO, that degree of protection is overkill
anyway and so i not an issue with me!<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:
GS wrote:
GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

No cases that I'm aware of!



Thanks
I will try it.
I do no need anything more just VBA protection.

It doesn't do anything else. It renders the same 'effect' as JKP's
shared workbook trick, (which as you probably know can be undone) by
altering the binary at various levels. Only admitted flaw to date is
that if you use the 'optional' advanced protection it loses a level when
you save your file. IMO, that degree of protection is overkill anyway
and so i not an issue with me!<g

It did not work. pivot tables, external data. I do not remember exactly
why I couldn't use it.

GS wrote:
GS wrote:
GS wrote:

Unviewable+
It's not free!

Did you have a case when it did not work?

No cases that I'm aware of!



Thanks
I will try it.
I do no need anything more just VBA protection.

It doesn't do anything else. It renders the same 'effect' as JKP's
shared workbook trick, (which as you probably know can be undone)
by
altering the binary at various levels. Only admitted flaw to date
is
that if you use the 'optional' advanced protection it loses a level
when
you save your file. IMO, that degree of protection is overkill
anyway
and so i not an issue with me!<g

It did not work. pivot tables, external data. I do not remember
exactly why I couldn't use it.

My understanding is that the latest release of unviewable+ 'just
works'! I don't use it myself but I've done extensive work with another
monitor of these NGs (who is a MVP I will not name). I do know the
issues you cite are common with shared workbooks and so I suspect any
methodology that messes with anything to do with that feature will
cause trouble.

Of course, there's always the option to go DLL or COMAddin!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:
Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do not
want client to add anything to VBA.

What I do is more like document facing project . File can be send around
the world.
I can't install anything. All VSTO or DLL requiring registration with
admin right can't be used.

GS wrote:
Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do not
want client to add anything to VBA.

What I do is more like document facing project . File can be send
around the world.
I can't install anything. All VSTO or DLL requiring registration with
admin right can't be used.

Not even if your installer runs with elevated permissions?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:
GS wrote:
Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do not
want client to add anything to VBA.

What I do is more like document facing project . File can be send
around the world.
I can't install anything. All VSTO or DLL requiring registration with
admin right can't be used.

Not even if your installer runs with elevated permissions?


Clients do not have rights to install anything.
They work on virtual desktops and every time they login they see brand
new computer. Nothing stays except data on shared drives.

They other reason is that they do not want to install anything.
They want to open excel file, do their work and send that file to
another person.
I call that iPhone syndrome. One button click and nothing more advanced.

GS wrote:
GS wrote:
Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do
not
want client to add anything to VBA.

What I do is more like document facing project . File can be send
around the world.
I can't install anything. All VSTO or DLL requiring registration
with
admin right can't be used.

Not even if your installer runs with elevated permissions?


Clients do not have rights to install anything.
They work on virtual desktops and every time they login they see
brand new computer. Nothing stays except data on shared drives.

They other reason is that they do not want to install anything.
They want to open excel file, do their work and send that file to
another person.
I call that iPhone syndrome. One button click and nothing more
advanced.

Yes, I get that. My solution for portable apps (run from USB drive) is
to run DLLs reg-free via LoadLibrary(). No reason you can't do same
other than it requires you ship the DLL with your workbook. This
clearly won't work in your scenario!

Perhaps you can have someone using a current release unviewable+ lock
your VBA project so you can give it a test drive!?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

GS wrote:
GS wrote:
GS wrote:
Of course, there's always the option to go DLL or COMAddin!

I did it about 7 years ago.
I moved all calculation logic to C++
Unfortunately a couple of things must stay in VBA or we simply do not
want client to add anything to VBA.

What I do is more like document facing project . File can be send
around the world.
I can't install anything. All VSTO or DLL requiring registration with
admin right can't be used.

Not even if your installer runs with elevated permissions?


Clients do not have rights to install anything.
They work on virtual desktops and every time they login they see brand
new computer. Nothing stays except data on shared drives.

They other reason is that they do not want to install anything.
They want to open excel file, do their work and send that file to
another person.
I call that iPhone syndrome. One button click and nothing more advanced.

Yes, I get that. My solution for portable apps (run from USB drive) is
to run DLLs reg-free via LoadLibrary(). No reason you can't do same
other than it requires you ship the DLL with your workbook. This clearly
won't work in your scenario!

Aplication.RegisterXLL
It solves a lot of problems with complicated calculation processes and
does not require any registration.



Perhaps you can have someone using a current release unviewable+ lock
your VBA project so you can give it a test drive!?

I will try it when I find a minute free time.

9 de mayo de 2016, Hi Jan, i try to do this with excel 2011 for mac, but it didn´t work.
there are something leatherlike this in excel 2011 mac ?



El domingo, 17 de enero de 2010, 12:50:40 (UTC-5), Jan Karel Pieterse escribió:
Hi Ron,

Is there a better more secure way to protect a VBA project?

Yes there is (misplaced the link to this one):

1. Save the Excel workbook (.xls) file into an add-in (File SaveAs.....)
2. After you have the saved add-in (.xla), close the Excel workbook (.xls)
3. Double click on the add-in to open it
4. Press Alt+F11 to access the add-in's vba project
5. Lock the vba-project with a password
6. Double-click on the "ThisWorkbook" code module
7. Press F4 to open the Properties window
8. Change the "IsAddin" status to FALSE
9. Return to Excel by Pressing Alt+Q (or close the vbe window)
10. Go to Tools Share Workbook
11. When the dialogue appears, check the box for: (Allow changes by.....)
12. Press OK to close the Dialogue
13. When prompted to save, Press OK
14. Press Ok to accept that "macros cannot be accessed"
15. You should feel giddy at this point because you just realized what you have
been missing right under your nose
16. Verify that the [SHARED] appears in the application title bar
17. Now save the workbook again as an Add-in (File SaveAs...) overwriting the
previous one
18. Close this Excel workbook without saving the changes (you don't need it)
19. Test out your newly saved add-in (open it, access the vbe, try to expand
the project window, you should get the new message "Project is Unviewable"
20. Your done

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

I just don't understand, GS and Witek, Why everyone in this world wants everything for Free? Particularly, even when you can afford to pay?

Please do appreciate someone's efforts at-least...

I am new to this work.. @57.

But couldn't resist responding, even after 2 yeas of last post..

Cheers Guys..

Ajay

On Friday, November 27, 2015 at 11:12:49 PM UTC+5:30, GS wrote:
hi,

I have tried JKP process and it works but my file contains web quires
and when try to run it shows runtime error 1004 is there any
solution for this?

regards,

Prashant

Unviewable+
It's not free!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

ajaypunjani wrote:

I just don't understand, GS and Witek, Why everyone in this world wants
everything for Free? Particularly, even when you can afford to pay?

Please do appreciate someone's efforts at-least...

I am new to this work.. @57.

But couldn't resist responding, even after 2 yeas of last post..

"Free" is not necessarily a bad thing. All of my publicly-available projects
have been released for free. (Also open source, a not-entirely-related
subject.)

I'm not willing to dig out the old thread just to get some context, but as a
general rule, why should I pay for something when there's something else just
as good (or almost so) that is free? It doesn't matter whether or not I can
afford it.

--
I always hated kids.

Thank you Jan..

It worked perfect for me. I hope this cannot be further broken by any means?? Actually an year of my work got stolen by another person by a readily available software from google. Thanks a lot man!! This is a savior. I hope this is the ultimate sacurity?? Please let me know.

Thanks

With best regards
Hasan

On Sunday, January 17, 2010 at 11:20:40 PM UTC+5:30, Jan Karel Pieterse wrote:
Hi Ron,

Is there a better more secure way to protect a VBA project?

Yes there is (misplaced the link to this one):

1. Save the Excel workbook (.xls) file into an add-in (File SaveAs.....)
2. After you have the saved add-in (.xla), close the Excel workbook (.xls)
3. Double click on the add-in to open it
4. Press Alt+F11 to access the add-in's vba project
5. Lock the vba-project with a password
6. Double-click on the "ThisWorkbook" code module
7. Press F4 to open the Properties window
8. Change the "IsAddin" status to FALSE
9. Return to Excel by Pressing Alt+Q (or close the vbe window)
10. Go to Tools Share Workbook
11. When the dialogue appears, check the box for: (Allow changes by.....)
12. Press OK to close the Dialogue
13. When prompted to save, Press OK
14. Press Ok to accept that "macros cannot be accessed"
15. You should feel giddy at this point because you just realized what you have
been missing right under your nose
16. Verify that the [SHARED] appears in the application title bar
17. Now save the workbook again as an Add-in (File SaveAs...) overwriting the
previous one
18. Close this Excel workbook without saving the changes (you don't need it)
19. Test out your newly saved add-in (open it, access the vbe, try to expand
the project window, you should get the new message "Project is Unviewable"
20. Your done

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

It works for me. If you follow the steps given by Jan it works perfectly unless if you have tables or XML. May I know what is the error message that you get.. Thanks

On Friday, February 6, 2015 at 5:23:01 PM UTC+5:30, wrote:
Hi Karel

Does it works also with office 2010,
becouse I follow all the steps but it does't work :-(

Thank you in advanced
Carlo

On Sunday, January 17, 2010 at 11:20:40 PM UTC+5:30, Jan Karel Pieterse wrote:
Hi Ron,

Is there a better more secure way to protect a VBA project?

Yes there is (misplaced the link to this one):

1. Save the Excel workbook (.xls) file into an add-in (File SaveAs.....)
2. After you have the saved add-in (.xla), close the Excel workbook (.xls)
3. Double click on the add-in to open it
4. Press Alt+F11 to access the add-in's vba project
5. Lock the vba-project with a password
6. Double-click on the "ThisWorkbook" code module
7. Press F4 to open the Properties window
8. Change the "IsAddin" status to FALSE
9. Return to Excel by Pressing Alt+Q (or close the vbe window)
10. Go to Tools Share Workbook
11. When the dialogue appears, check the box for: (Allow changes by.....)
12. Press OK to close the Dialogue
13. When prompted to save, Press OK
14. Press Ok to accept that "macros cannot be accessed"
15. You should feel giddy at this point because you just realized what you have
been missing right under your nose
16. Verify that the [SHARED] appears in the application title bar
17. Now save the workbook again as an Add-in (File SaveAs...) overwriting the
previous one
18. Close this Excel workbook without saving the changes (you don't need it)
19. Test out your newly saved add-in (open it, access the vbe, try to expand
the project window, you should get the new message "Project is Unviewable"
20. Your done

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com

Hi Jan/All

Also for one of my other projects I have TABLES. Is there any workaround for making this work for Workbooks with tables?? Thanks in Advance

er.hasanmj wrote:

It worked perfect for me. I hope this cannot be further broken by any
means?? Actually an year of my work got stolen by another person by a
readily available software from google. Thanks a lot man!! This is a
savior. I hope this is the ultimate sacurity?? Please let me know.

The original post was ***EIGHT ****ING YEARS AGO!!!***

On Sunday, January 17, 2010 at 11:20:40 PM UTC+5:30, Jan Karel Pieterse
^^^^^^^^^^^^^^^^^^^^^^^^^^^

Do you really think Jan is still waiting around for more replies to this
thread? (Hint: No.)

--
What's a "Bunsen" anyway? And why would you want to burn one?