Article ID: 289885 - Last Review: January 26, 2005 - Revision: 6.1 Description of how to help protect a Microsoft Access database
This article was previously published under Q289885 Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
For a Microsoft Access 2000 version of this article, see 254372
(http://support.microsoft.com/kb/254372/
)
.
SUMMARY
This article provides an overview of how you can help protect 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. MORE INFORMATION
When you are creating a database, there are three common mistakes that enable Access users to circumvent security:
REFERENCES
For additional information about how to protect the Visual Basic Environment, click the following article number to view the article in the Microsoft Knowledge Base:
223447
(http://support.microsoft.com/kb/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 an Access database in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.For more information about setting user-level security, click Microsoft Access Help on the Help menu, type secure an access database by using the user-level security wizard in the Office Assistant or the Answer Wizard, and then click Search to view the topic.
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
