I can still interrupt my login screen by pressing CTRL + BREAK and enter the VBA EDITOR.
I re-read the posts. I believe the above in Post #13 gets to the heart of the matter concerning your ultimate goal.


Excel has a few built in methods that "attempt" to provide security. HOWEVER, these security measures are only effective
against users who are absolutely EXCEL challenged. In other words ... they have no idea how EXCEL works behind the scenes
and more importantly, don't care. They have no interest in viewing / learning / editing the code. The Internet is loaded with
example code to break through EXCEL's built in security measures.

There are different measures / macros / add ons / etc. that have been created through the years, intending to make EXCEL more secure
or even 'inpenetrable' by anyone except the coder. Problem is ... all of these methods have been proven to be inadequate.

I myself have searched for several years for a means to protect my code ... no luck.

There are two methods that might possibly work ... but there is a cost.

#1 If you could compile your workbook into an executable file, just like any other commercial program, that would stop almost everyone except the hackers from
getting your code. Problem is ... no one has created a means of making an Excel workbook into an executable program. I've investigated some of the commercial
programs sold on the Internet that claim to make Excel into an executable. They don't work. I've been able to break their code that wraps around the workbook code.

#2 You could use a program that "scrambles" your code into unrecognizable gibberish. Here is an example : https://www.excel-pratique.com/en/vb...obfuscator.php
My personal opinion is this is probably the most effective means of protecting your code. There is a downside to using an obfuscator .... every program I've tried either wouldn't
obfuscate every word / character / string in the macros ... and this would allow a good coder to piece together the code to the original format. OR ... the obfuscator would
do it's trick on everything but the macros wouldn't run. You will have to go back into the obfuscated code and located the key words in the macro commands and return
those back to the original form.

A few examples of this are the terms: SUB, INTEGER, CONST, DIM, FOR, IF, NEXT, etc. In a few of the cases I had to leave a large portion of the original coding in place for the macro/s to run. This
made the obfuscator totally useless in my mind because it wasn't doing the job I paid good money for it to do.

If you are able to locate a means to totally protect macro code, please let me and others know. Sorry but I can't assist you with the search ... I've been there / done that and came up empty handed.