Editing Microsoft Access (section)

== Protection ==
Microsoft Access applications can be made secure by various methods, the most basic being password access control; this is a relatively weak form of protection.

A higher level of protection is the use of workgroup security requiring a [[User (computing)|user name]] and [[password]]. Users and groups can be specified along with their rights at the [[object type]] or individual object level. This can be used to specify people with read-only or data entry rights but may be challenging to specify. A separate workgroup security file contains the settings which can be used to manage multiple databases. Workgroup security is not supported in the Access 2007 and Access 2010 ACCDB database format, although Access 2007 and Access 2010 still support it for MDB databases.

Databases can also be encrypted. The ACCDB format offers significantly advanced encryption from previous versions.<ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/bb421308.aspx|title=Security Considerations and Guidance for Access 2007|date=May 5, 2014|publisher=Microsoft|access-date=March 13, 2016}}</ref>

Additionally, if the database design needs to be secured to prevent changes, Access databases can be locked/protected (and the source code [[compiled]]) by converting the database to a .MDE file. All changes to the VBA project (modules, forms, or reports) need to be made to the original MDB and then reconverted to MDE. In Access 2007 and Access 2010, the ACCDB database is converted to an ACCDE file. Some tools are available for unlocking and "[[decompiling]]", although certain elements including original VBA comments and formatting are normally irretrievable.