|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Access AND Security PermissionsWe currently have novell and have opted not to place security within the
database itself, but utilized novell security of having Read & File Scan for folks we don't want editing and full rights for folks that need to edit the database. Now we are moving to Microsoft and we do NOT want to start setting up and utilizing the Access internal security, but would prefer to place the security at the windows level. Can someone assist if this is possible and what type of security permissions would be needed at the directory level? We have no need to utilize the internal security to secure reports, forms, etc. Also, we have been burnt a few times by utilizing an MDW when someone has left the company and people's name change (which happens quite frequently). "SkyEyes" <SkyE***@discussions.microsoft.com> wrote in message news:1FD0FD04-50DB-47E7-A1A6-D51FFF9D645C@microsoft.com... Set up a folder that has the necessary permissions for only the group of people that need to use the database. Other users shouldn't have any permission to that folder. That group will need read/write/create permission on the folder. All users need create permission in order to create the associated ldb file-without it, the first person in will open the mdb exclusively.> We currently have novell and have opted not to place security within the > database itself, but utilized novell security of having Read & File Scan for > folks we don't want editing and full rights for folks that need to edit the > database. > > Now we are moving to Microsoft and we do NOT want to start setting up and > utilizing the Access internal security, but would prefer to place the > security at the windows level. > Also, we have been burnt a I can't for the life of me see how that is the fault of Access security.> few times by utilizing an MDW when someone has left the company and people's > name change (which happens quite frequently). -- Joan Wild Microsoft Access MVP What about delete rights...how does that work within windows security. Just
because it the person didn't have delete rights and they were the last person out of the ldb file, the file just sat out there and eventually caused problems. Show quote "Joan Wild" wrote: > "SkyEyes" <SkyE***@discussions.microsoft.com> wrote in message news:1FD0FD04-50DB-47E7-A1A6-D51FFF9D645C@microsoft.com... > > We currently have novell and have opted not to place security within the > > database itself, but utilized novell security of having Read & File Scan for > > folks we don't want editing and full rights for folks that need to edit the > > database. > > > > Now we are moving to Microsoft and we do NOT want to start setting up and > > utilizing the Access internal security, but would prefer to place the > > security at the windows level. > > Set up a folder that has the necessary permissions for only the group of people that need to use the database. Other users shouldn't have any permission to that folder. That group will need read/write/create permission on the folder. All users need create permission in order to create the associated ldb file-without it, the first person in will open the mdb exclusively. > > > Also, we have been burnt a > > few times by utilizing an MDW when someone has left the company and people's > > name change (which happens quite frequently). > > I can't for the life of me see how that is the fault of Access security. > > -- > Joan Wild > Microsoft Access MVP > Although it isn't *absolutely* necessary, your life might be easier if you put delete permission on the folder as well, for the reason you point out.
If you're concerned about a user deleting a file, hide the share: \\servername\share$ rather than \\servername\share -- Joan Wild Microsoft Access MVP Show quote "SkyEyes" <SkyE***@discussions.microsoft.com> wrote in message news:DE2A6F40-4981-48EA-92AC-6168B954F121@microsoft.com... > What about delete rights...how does that work within windows security. Just > because it the person didn't have delete rights and they were the last person > out of the ldb file, the file just sat out there and eventually caused > problems. > > "Joan Wild" wrote: > >> "SkyEyes" <SkyE***@discussions.microsoft.com> wrote in message news:1FD0FD04-50DB-47E7-A1A6-D51FFF9D645C@microsoft.com... >> > We currently have novell and have opted not to place security within the >> > database itself, but utilized novell security of having Read & File Scan for >> > folks we don't want editing and full rights for folks that need to edit the >> > database. >> > >> > Now we are moving to Microsoft and we do NOT want to start setting up and >> > utilizing the Access internal security, but would prefer to place the >> > security at the windows level. >> >> Set up a folder that has the necessary permissions for only the group of people that need to use the database. Other users shouldn't have any permission to that folder. That group will need read/write/create permission on the folder. All users need create permission in order to create the associated ldb file-without it, the first person in will open the mdb exclusively. >> >> > Also, we have been burnt a >> > few times by utilizing an MDW when someone has left the company and people's >> > name change (which happens quite frequently). >> >> I can't for the life of me see how that is the fault of Access security. >> >> -- >> Joan Wild >> Microsoft Access MVP >>  |
|||||||||||||||||||||||
Other interesting topics