|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (7 bit)
Join Date: Dec 2000
Posts: 105
|
win2K permissions, "delete" problem
hi, hope I explain this properly...
I have a folder that contains customer data sheets, with a subfolder that contains drafts of the data sheets. I have 2 Groups "A" and "B" Group "A" can read the the data sheets in the main folder. Group "B" creates the data sheets, and has full control of both folders, except for "delete" and "delete sub folders and files" The problem lies in that once a new data sheet is created, "Group B" can't delete the old ones. They cant move the old files to the subfolder either, since that requires a delete. I removed the delete permissions to prevent "oopps" from happening. Is there a way to do this? All help greatly appreciated. Thanks |
|
|
|
|
|
#2 |
|
Professional gadfly
|
I don't think so. Either you can give them delete permissions to delete files or not. By preventing mistakes, you are also preventing them from deleting things on purpose.
It would be nice if there was a way to deny delete permission to those people who aren't paying attention, or copied down the wrong file name, but I think that is a ways off yet. ![]() If you are more worried about losing critical data than having too much data lying around in the wrong places, I would keep it as is and have somebody you trust do the cleanup. |
|
|
|
|
|
#3 |
|
Member (7 bit)
Join Date: Dec 2000
Posts: 105
|
thanks for the quick reply doctorgonzo, appreciated
I run daily back-ups, and can pretty much trust those in the group who create the files, but accidents do happen. I was hoping there was some "sneaky" way of allowing a file move but not include delete, so that only the current version of a file is left in the main folder. This is to prevent the general users of the other group from working off of old files that have been updated. Maybe if I create a naming convention where a file gets "OLD" appended to the title? ie " myfile_OLD.doc" when an updated version is created. Then I could do a weekly clear-out. I can let the one group have permissions for that. I guess it boils down to staff training, and accepting that I can't always delegate some tasks. |
|
|
|
|
|
#4 |
|
Professional gadfly
|
The sneaky way of moving a file without deleting it is to simply copy the file to a new place. All a move is really is copying a file to a new place and then deleting the old file. There is always a delete involved.
Renaming a file would work if it was done consistently. |
|
|
|
|
|
#5 |
|
Member (7 bit)
Join Date: Dec 2000
Posts: 105
|
I think we have worked out a solution here.. since these files are the "property" of one department, I can request a naming / copying schema be followed if they chose to have the ability to delete in their folder. This way if they mess up and delete, and have to revert to last nights back-up.. I can say " go see Joe... he deleted the file.."
Would likely only happen once before "Joe" remembers the rules. heh |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|