probably better setting up a userform that shows on open and asks for a password - you can then easily track attempts and close the app as and when you wish
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
You can then also write a date & time value into the file somewhere (Assume you want a half hour window say) and then have the code instantly close it if it is opened again within that window of time.
Regards
Ken...........
---------------------------------------------------------------------------- It's easier to beg forgiveness than ask permission
----------------------------------------------------------------------------
The user form is a good idea, but it won't work for this current project b/c I don't want to deter the ordinary user from entering data into the workbook.
I just have a couple of people who insist on cracking the password, then changing the functions... and wondering why it doesn't work. Unfortunately, terminating these people is out of the question.
worksheet I can understand but if they are cracking workbook passwords, there will be very little you can do other than wrapping the workbook up in a VB project....
Rgds, Geoff
We could learn a lot from crayons. Some are sharp, some are pretty and some are dull. Some have weird names and all are different colours but they all live in the same box.
Even that isn't safe now. A hex editor and changing the right string of values, and the VBA protection is toast.
Regards
Ken............
---------------------------------------------------------------------------- It's easier to beg forgiveness than ask permission
----------------------------------------------------------------------------
---------------------------------------------------------------------------- It's easier to beg forgiveness than ask permission
----------------------------------------------------------------------------
If you like to stay purely in excel, separate data and code by creating password protected add-in. Next this dirty thing can protect from cracking vba project: with hex editor try to find and clear (to 0s or other values) some of not compiled code (excel, unlike access, doesn't remove uncompiled code from the add-in).
Any saving or unprotecting of such file will crash excel. The add-in is here to avoid temporary saving the file. And test the stability for the add-in on your machines.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.