Description of how to help protect a Access 2000 database (254372)
The information in this article applies to:
This article was previously published under Q254372 For a Microsoft Access 97 version of this article,
see
132143. Moderate: Requires basic macro,
coding, and interoperability skills. This article applies only to a
Microsoft Access database (.mdb). For a Microsoft Access
2002 version of this article, see
289885. SUMMARY 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. REFERENCES The Access Security Manager Add-In presents all security
settings in a single view, so the administrator can set and display permission
settings and assign ownership with all of the information necessary to make
informed decisions. For additional
information about the Access Security Manager Add-In, click the following
article numbers to view the articles in the Microsoft Knowledge Base: 235961
Microsoft Access Security Manager Add-In Is Available in the Download Center
223447 ACC2000: Can't Secure Individual Modules in Access 2000
For more information
about how to secure a database in Microsoft Access, click Microsoft Access Help on the Help menu, type secure a Microsoft Access
database in the Office Assistant or the Answer Wizard, and then
click Search to view the topics returned. For
more information about how to set user-level security, click Microsoft
Access Help on the Help menu, type secure
a database using the user-level security wizard in the Office
Assistant or the Answer Wizard, and then click Search to view
the topic.
Modification Type: | Minor | Last Reviewed: | 1/26/2005 |
---|
Keywords: | kbpermissions kbpasswords kbopenfile kbprivacy kbsavefile kbDatabase kbhowto kbinfo kbusage KB254372 |
---|
|