Password

[Jakeman]

Is it possible to protect (All Access Objects) “Macros” with a PASSWORD so that an user cannot change coding?

 

[boblarson]

Compile it to an ACCDE or MDE (depending on your version) and then nobody can do anything with macros or modules (nor with form design or report design).

Be sure to save the master ACCDB or MDB file for making changes to it but distribute the compiled version.

 

[Jakeman]

Thanks So Much Bob for the info.
TakeCare, Jake

 

[AccessJunkie]

To expand on Bob's reply for clarification, compiling your database into a MDE or ACCDE won't protect you from people changing *standalone* macro objects - macros that appear in the Navigation Pane. With MDEs and ACCDEs, users can still open macro objects in Design View, make changes, and then save those changes.

If you use *embedded* macros, then you can prevent users from tampering with the actions in your macros. Embedded macros (new in 2007) are macros embedded into the form or report itself. If you compile your database into an MDE or ACCDE then users can't open your forms and reports in Design View, and thus they can't modify the embedded macro logic you've saved inside those objects.

--------------------
Jeff Conrad - Access Junkie - MVP Alumnus
SDET II - Access Test Team - Microsoft Corporation

Author - Microsoft Access 2010 Inside Out
Co-author - Microsoft Office Access 2007 Inside Out
Access 2007/2010 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------

 

[boblarson]

To expand on Bob's reply for clarification, compiling your database into a MDE or ACCDE won't protect you from people changing *standalone* macro objects - macros that appear in the Navigation Pane. With MDEs and ACCDEs, users can still open macro objects in Design View, make changes, and then save those changes.

Jeff - That is interesting information. I have always been under the impression that it was only Tables and Queries you could change in an MDE. So, I need to change what I've been stating from here on out.

eeek!

 

[AccessJunkie]

No worries Bob, glad to assist.

--------------------
Jeff Conrad - Access Junkie - MVP Alumnus
SDET II - Access Test Team - Microsoft Corporation

Author - Microsoft Access 2010 Inside Out
Co-author - Microsoft Office Access 2007 Inside Out
Access 2007/2010 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------

 

[theron82owen]

Instead of protecting the macros with password, compilation will prove to be more secure.

 

[boblarson]

Instead of protecting the macros with password, compilation will prove to be more secure.

INCORRECT - did you not read the answer from Jeff Conrad who works on the Access Team at Microsoft? Or is this just a lame post in anticipation of spamming or trying to add a URL with a spam signature?

 

[thingssocomplex]

The 2010 Inside Out is great help to me cheers Jeff for publishing

 

[AccessJunkie]

The 2010 Inside Out is great help to me cheers Jeff for publishing

You're very welcome. I'm pleased to hear you found my book useful.
Good luck with your continued Access studies.

--------------------
Jeff Conrad - Access Junkie - MVP Alumnus
SDET II - Access Test Team - Microsoft Corporation

Author - Microsoft Access 2010 Inside Out
Co-author - Microsoft Office Access 2007 Inside Out
Access 2007/2010 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------