Workbook_Open Check UserName

While it is possible to have code check the username and close, the end user can still open and browse the workbook if macros are not enabled.

Originally Posted by nordicdust

As mc84excel mentioned, if they do not have macro enabled, your security will not work.

This will help on that.

' Event handler before closing application

Please Login or Register  to view this content.

And unhide them in the workbook open.

• If an approved user doesn't choose to Save on workbook close then the workbook sheets will be visible to the next person who opens the workbook with macros disabled.
• If Excel crashes on an approved user then then it is possible that the same situation will occur.

While Excel security is inherently flimsy, there are actions that can be taken to increase the protection of your project from casual snoopers.
For instance - hijack the Save event and replace it with your own custom version that will apply the xlVeryHidden so that the workbook is always saved with the sheets hidden. By doing this, the protection wont break if the user forgets to save or if their Excel session crashes. Nor does this protection depend on the next end user having macros enabled when opening the workbook.
This custom save event is part of a concept known as 'Force user to enable macros'. A quick online search should return several different versions of this code (with varying degrees of quality). Pick one you like.

If you have not already done so, you will need to password protect your VBA project to prevent others from viewing the code.


Additional comments:

1. While the 'force enable macros' concept will increase the protection of your workbook, don't ever assume that this has made you secure. You cant prevent a skilled Excel user from getting in if they really wanted to.
2. If you want to increase your security, I don't recommend leaving the usernames in a workbook sheet. VeryHidden or not. It would be more safe if all usernames were hardcoded into the VBA project instead. (Again, doing this will help but it will never be perfectly safe. VBA protection can be bypassed too)