Locking VBA project with code

[KitaYama]

The title says it all.

Is it possible to lock/unlock VBA project of a accdb file with code (vba)?

Thanks.

 

[theDBguy]

Just off the top of my head (can't do any testing right now), but probably possible from an external app.

 

[KitaYama]

I'd appreciate if you have any code for that.
Not in a hurry. Whenever you have enough free time to check.

Thanks.

 

[Josef P.]

I think it only works with SendKeys or something similar.

Locking:

Solved - Locking a Access VBA Project programmatically

Is it possible to lock a VBA project with VBA instead of doing it manually by going to the Tools menu, select Properties and protection tab? Best Regards

www.access-programmers.co.uk

Solved - Application.VBE.ActiveVBProject.Protection

Buenas tardes. I'm looking for a way to remove the VBA project protection (I know the password), set the project name, and then put the same password back. I have this: If Application.VBE.ActiveVBProject.Protection = 0 Then...

www.access-programmers.co.uk

The best lock is a compiled file (accde).

 

[isladogs]

Danke schön @JosefP.
I knew I had answered the question before but hadn't searched for the link

Solved - Locking a Access VBA Project programmatically

Is it possible to lock a VBA project with VBA instead of doing it manually by going to the Tools menu, select Properties and protection tab? Best Regards

www.access-programmers.co.uk

@KitaYama
Although it can be done, do note the many caveats mentioned in that thread
1. It requires the use of SendKeys and the characters required are language dependant
2. VBA password protection is easily bypassed
3. Even when locked, a list of all procedures together with arguments is still accessible unless you use Option Private Module
4. Option Private Module is only available for Standard/Class Modules. A list of procedures etc in Form/Report modules is still visible.

Taken together, locking a project is of limited value and I rarely bother.
Use it as one part of a set of security measures but don't rely on it alone

 

[KitaYama]

@Josef P. @isladogs

I’m aware of the risks and how locking a vba project is of a limited value.
I was reading @isladogs’ security article and testing one of his demo databases.
Disabling shift by pass, hiding navigation pane and editing start up properties was done with code. I just wondered why I couldn’t find any code for locking the project.
My question was out of curiosity and not that I‘m planing to use it.

Thanks for solving the puzzle.

 

[isladogs]

The article deliberately leaves out several details. Partly because I don’t want to provide information to help hackers. I also avoid the use of SendKeys wherever possible.

 

[ebs17]

Counter-question: What is the special background to the desire for lock/unlock? A new front end is simply exchanged.
Design changes at runtime by the user are regularly an expression of previous deficiencies in the application.
The developer himself does not have to temporarily lock and therefore unlock anything.

 

[Josef P.]

I think it only works with SendKeys or something similar.

only

Just stumbled across this by accident while looking for something else in the WizHook class:
WizHook.SetVbaPassword
SendKeys is therefore not required for setting.

Looked up Thomas WizHook collection for safety:

Willkommen bei Team-Moeller.de - SetVbaPassword

Homepage von Team-Moeller.de Access

team-moeller.de

 

[isladogs]

I wrote an updated article about the Wizhook object last year which builds on the excellent information by Thomas Moller

Wizhook

A detailed reference guide to the hidden, undocumented but very useful Access WizHook object and its members

www.isladogs.co.uk

The Wizhook.SetVBAPassword function does allow you to set the vba project password where it is blank but it does not allow you to change an existing password. Therefore it is less useful than it could have been.