Eric Brodeur
asked on
Protecting Access database files using NTFS permission
I'm looking to protect an Access database using OS-based file permissions rather than placing the data into an SQL server.
I have split my Access application in two parts: program code MDB and database tables MDB. Can I place the database MDB onto a Windows Server folder and restrict the ability to delete the file?
If so, what file permissions should I apply?
If not, what do you recommend?
I have split my Access application in two parts: program code MDB and database tables MDB. Can I place the database MDB onto a Windows Server folder and restrict the ability to delete the file?
If so, what file permissions should I apply?
If not, what do you recommend?
that info above taken from http://cc.jlab.org/docs/services/windows/ntfs_permissions.html
ASKER
I understand how to apply NTFS permissions.
What I want to accomplish is allowing the user to Write to the folder containing the MDB but not Delete it. I doubt Access will work properly without Modify (read/write/delete) permissions.
Before I spent any time trying it I thought I'd ask the community and see what responses came back.
What I want to accomplish is allowing the user to Write to the folder containing the MDB but not Delete it. I doubt Access will work properly without Modify (read/write/delete) permissions.
Before I spent any time trying it I thought I'd ask the community and see what responses came back.
ASKER
On a whim I researched LDB files and found an EE topic which referrs to MS KB article 136128, "ACC: Introduction to .ldb Files (95/97)". The bottom of the article states:
Required Folder Permissions
If you plan to share a database, the .mdb file should be located in a folder where users have read, write, create, and delete (or full control) permissions. Even if you want users to have different file permissions (for example, some read-only and some read-write), all users sharing a database must have read, write, and create permissions to the folder. You can, however, assign read-only permissions to the .mdb file for individual users while still allowing full permissions to the folder.
I performed the above steps and it does exactly what I need. I applied Modify permissions to the folder and Read/Execute/Write permissions to the MDB files. This allows Access the freedom to manage LDB files while disallowing users from deleting the MDB files.
This question can be closed and points refunded.
Required Folder Permissions
If you plan to share a database, the .mdb file should be located in a folder where users have read, write, create, and delete (or full control) permissions. Even if you want users to have different file permissions (for example, some read-only and some read-write), all users sharing a database must have read, write, and create permissions to the folder. You can, however, assign read-only permissions to the .mdb file for individual users while still allowing full permissions to the folder.
I performed the above steps and it does exactly what I need. I applied Modify permissions to the folder and Read/Execute/Write permissions to the MDB files. This allows Access the freedom to manage LDB files while disallowing users from deleting the MDB files.
This question can be closed and points refunded.
Can u post a question in community support to close this down
No objections from me
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What if u placed the file in a folder then shared that folder?
I believe in Windows, u can specify what users have access to that share
U can also set on folders and/or files
You can assign multiple permissions to a user account by assigning permissions for a resource to an individual user account and to each group of which the user is a member.
A user's effective permissions for a resource are the sum of the NTFS permissions that you assign to the individual user account and to all of the groups to which the user belongs. If a user has Read permission for a folder and is a member of a group with Write permission for the same folder, the user has both Read and Write permission for that folder.
By default, permissions that you assign to the parent folder are inherited by and propagated to the subfolders and files that are contained in the parent folder
Files and subfolders can inherit permissions from their parent folder. Whatever permissions you assign to the parent folder can also apply to subfolders and files that are contained within the parent folder, depending on the inheritance option set for a given object. When you assign NTFS permissions to give access to a folder, you assign permissions for the folder and for any existing files and sub folders, as well as any new files and subfolders that are created in the folder.
You can prevent permissions that are assigned to a parent folder from being inherited by subfolders and files that are contained within the folder by setting an inheritance option set for a given object. That is, the subfolders and files will not inherit permissions that have been assigned to the parent folder containing them.
If you prevent permissions inheritance for a folder, that folder becomes the top parent folder. Permissions assigned to this folder will be inherited by the subfolders and files that it contains.
NTFS Folder Permissions
--------------------------
Full Control
Change permissions, take ownership, and delete subfolders and files, plus perform actions permitted by all other NTFS folder permissions
Modify
Delete the folder plus perform actions permitted by the Write permission and the Read & Execute permission
Read & Execute
Move through folders to reach other files and folders, even if the users do not have permission for those folders, and perform actions permitted by the Read permission and the List Folder Contents permission
List Folder Contents
See the names of files and subfolders in the folder
Read
See files and subfolders in the folder and view folder ownership, permissions, and attributes (such as Read-only, Hidden, Archive, and System)
Write
Create new files and subfolders within the folder, change folder attributes, and view folder ownership and permissions
NTFS File Permissions
-------------------------
Full Control
Change permissions and take ownership, plus perform the actions permitted by all other NTFS file permissions
Modify
Modify and delete the file plus perform the actions permitted by the Write permission and the Read & Execute permission
Read & Execute
Run applications plus perform the actions permitted by the Read permission
Read
Read the file, and view file attributes, ownership, and permissions
Write
Overwrite the file, change file attributes, and view file ownership and permissions
This talks about a webserver - its just for tips http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/986fda49-1e9f-4320-8fbb-81c9685fd58b.mspx?mfr=true