Why not provide some specific folder completely outside that tree for the temp to write to, and use a background process to sync the files from where the temp is putting them to their permanent home.
More moving parts, but *far* less effort overall. *ASB *(Professional Bio <http://about.me/Andrew.S.Baker/bio>) *Harnessing the Advantages of Technology for the SMB market... * On Tue, May 17, 2011 at 10:03 AM, <[email protected]> wrote: > > Greetings! > > We have a file server with a pretty convoluted directory tree... > > Anyway, our HR has hired a temp to scan documents and place it into a > specific folder. We do not want the temp to be able to write to any other > folders. (It would be nice to not have her able to open any files in any > other folders in that particular tree, but I'll settle for her having write > access to the specified folder.) > > Anyway, despite the attributes for the specified folder (currently set to > "Modify"), it appears the temp is denied write access. Probably something > further up the tree is causing a "no write" trait to be inherited by that > folder and thus is keeping files from being saved there. > > Temp can browse the network and open the folder. Temp can read a document > saved there. Temp cannot make changes to this document. > > What next to try? Thanks! > -- > richard > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
