1.What are the steps to secure a database?
2.In a nutshell, how does Microsoft Access security work?
3.What has changed in Microsoft Access security between Microsoft Access 2.0, Microsoft Access 95, and Microsoft Access 97?
3.1 Table 1: DAO Security Constants
4.How can I set a single password on my database?
4.1 Database Password Bugs
5.How can I clear a user's forgotten password?
6.What's the best way to convert my secured Microsoft Access 2.0 application to Microsoft Access 95 or Microsoft Access 97?
7.What's all this about a security hole in Microsoft Access 2.0?
8.How can I secure just my code without users having to log on?
9.How do I delete the Admin user?
10.How do I implement field-level or row-level security on my tables (RWOP or queries with Run Permissions set to Owners')?
11.Why can't I get my RWOP append query to run?
12.What is the difference between an "attached" table and a "linked" table?
13.How do I manage attached tables using Microsoft Access security?
14.What permissions are necessary to update table attachments?
14.1 Using RefreshLink to reattach tables
14.2 Using TransferDatabase to reattach tables
14.3 No Permissions necessary Using the Connect property to reattach tables
14.4 Error messages
15.Why do users require permission to create new tables in order to update a table attachment?
16.What happens when the front-end database permissions on an attached table differ from those in the back-end database?
16.1 Creating new links
16.2 What permissions should you set for <New Table/Queries>?
16.3 Updating or refreshing existing links/attachments
16.4 Synchronizing permissions
17.How can I retrieve the "most restrictive" permissions for attached tables?
18.Can I prevent users from attaching tables?
19.How do I work with a secured application and an unsecured application at the same time?
20.How do I keep users from viewing Code Behind Forms?
21.How can I tell who is logged on to my shared, networked application?
22.How can I obtain group and user membership information programmatically?
23.How can I obtain the groups that the current user belongs to without hard-coding an Admins ID and password in the code?
24.How can I prevent users from creating new objects in my database?
25.How can I prevent users from updating any tables from any means other than through forms?
26.How can I secure some parts of my application (an add-in), yet make others totally open to any Microsoft Access user?
27.How do I prevent users from holding down the SHIFT key to bypass the AutoExec macro?
28.How do I prevent a run-time application from being opened in full retail Microsoft Access?
29.Does Microsoft Access security still work if I use OLE automation or Microsoft Query to manipulate Microsoft Access tables?
30.How can I use the Security Wizard without creating an encrypted database?
31.When I use the Security Wizard in Microsoft Access 2.0, it runs to 99%, and then freezes
32.I thought I secured my database, but someone opened it with his or her own workgroup file. Is Microsoft Access security broken?
33.I want users in other groups besides the Admins group to be able to administer the database and add accounts
34.How can I "de-secure" a database?
35.I lost/forgot my password and can't get into my database
36.Do I need a separate workgroup file for every database I develop for my department?
37.How do I use DAO to manipulate permissions?
38.I created a user in code but the user isn't in the Users group and can't start Microsoft Access
39.I created a user and I can't log on as that user
40.I ran the Security Wizard but users from another workgroup can still open the database
41.How do I implement security when I am using Microsoft Visual Basic« 3.0 as a front-end?
42.Do I need to use a System.mda when I'm using Visual Basic to control secured objects?
43.How do I open a password-protected database from Visual Basic?
44.Additional sources of information
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.