JaedenRuiner
Registered User.
- Local time
- Today, 03:44
- Joined
- Jun 22, 2005
- Messages
- 154
Alright,
Now, I have Office 2003 pro, with Access, with which I am developing a project. Now, I have had much experience with databases, and have created many other Access mdb files as well. mostly for something simple, like creating a database of all my movies, or books, or something silly like that. I've even done one of my video game modification data to help keep me organized.
But those are home end, simple, and having absolutely zero necessity for security.
I am working on a professional level project now (a new thing for me specific to Access, but not to databases and applications). And Access has always confused me when it came to setting up security.
I understand how to set rights in databases, but i remember from some time ago reading that Access security was a royal pain, due to the "Admin" user being equated with "Everyone". So if i were to copy the mdb onto a flash drive, and take it over to my client and install it. Sure I may have set some "startup" settings and hidden some database objects, but from what i've before (and this was years ago) without some "special" security concerns, the everyday user at my client's company could alter those settings, restoring full access to the database, if they knew how, because as the "Admin" of their copy of Access, they are the "adminstrator" of the db.
So I need a point to a good and complete guide to Access User Level Security in Access 2003. I've seen links that talk about Access 2000, and Access 2007. But nothing that is concise, and clear about how to set this up.
Should I:
The 10 Steps
I found that url as well as a few other on MSDN that seem to describe some levels of how to do these things but nothing as "detailed" as I would prefer. And by detailed I mean in explanation of what they are, why we do these steps, because for me it is no just knowing what to do, but why to do it, so I can understand fundamental architecture and thus not need to ask such questions in the future. *smile*
Thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Now, I have Office 2003 pro, with Access, with which I am developing a project. Now, I have had much experience with databases, and have created many other Access mdb files as well. mostly for something simple, like creating a database of all my movies, or books, or something silly like that. I've even done one of my video game modification data to help keep me organized.
But those are home end, simple, and having absolutely zero necessity for security.
I am working on a professional level project now (a new thing for me specific to Access, but not to databases and applications). And Access has always confused me when it came to setting up security.
I understand how to set rights in databases, but i remember from some time ago reading that Access security was a royal pain, due to the "Admin" user being equated with "Everyone". So if i were to copy the mdb onto a flash drive, and take it over to my client and install it. Sure I may have set some "startup" settings and hidden some database objects, but from what i've before (and this was years ago) without some "special" security concerns, the everyday user at my client's company could alter those settings, restoring full access to the database, if they knew how, because as the "Admin" of their copy of Access, they are the "adminstrator" of the db.
So I need a point to a good and complete guide to Access User Level Security in Access 2003. I've seen links that talk about Access 2000, and Access 2007. But nothing that is concise, and clear about how to set this up.
Should I:
- Remove the Admin user from the Admins Group After I've created a separate "God" account under the Admins Group?
- Convert the File Format over to 2002-2003 from 2000, and are there any advantages? (Security wise or otherwise)
- Does The security wizard create a specific workgroup information file for this database only, or is it for the system, And Do I need to create one first before entering the User And Group Accounts setup dialog?
The 10 Steps
I found that url as well as a few other on MSDN that seem to describe some levels of how to do these things but nothing as "detailed" as I would prefer. And by detailed I mean in explanation of what they are, why we do these steps, because for me it is no just knowing what to do, but why to do it, so I can understand fundamental architecture and thus not need to ask such questions in the future. *smile*
Thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
