Article ID: 132143 - View products that this article applies to.
This article was previously published under Q132143
This article provides an overview of how you can secure a database so that it is not changed or copied by other Microsoft Access users.
This article assumes that you have a thorough understanding of the pieces that make up the Microsoft Access security model: workgroups, accounts, ownership, and permissions. For more information about the Microsoft Access security model, you can obtain the "Security Wizard and White Paper for Version 2.0" document.
For information about how to download the "Security Wizard and White Paper for Version 2.0," please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/122036/EN-US/ )ACC2: Security Wizard and White Paper for Access 2.0 Available
For an overview of how to secure a database in Microsoft Access version 7.0, search the Help index for "security, user-level security" and display the topic, "Secure a database using the Security Wizard."
For an overview of how to secure a database in Microsoft Access 97, search the Help index for "security, overview" and display the topic, "Secure a database." Scroll to the bottom of the topic and click the link to "Secure a database with the User-Level Security Wizard."
Three common mistakes you can make when you create a database that enable other Microsoft Access users to circumvent security are as follows:
Microsoft Access "Building Applications," version 2.0, Chapter 14, "Securing Your Application," pages 313-344
Article ID: 132143 - Last Review: January 19, 2007 - Revision: 4.2
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.