Create folders with specified viewship

Can you authoratively answer questions Q1-Q11? We want to (programmatically) create folders with the same view 'permissions' as existing folders. Imagine **Fred** can see Drive X or Folder X but **Mary** can't. Q1. Can Fred create a Folder Y not in Drive X or Folder X with the same viewship properties as Drive X or Folder X? Q2. For drives/files that Fred can see, can he create folders like this independently of his authority (ie he is not an admin typically)? Q3. Or is creating the new folder inside the other one the only way to do this? Q4. Can file permissions be set file by file? Q5. If Fred can see Mary's files can he always create folders there too (if Mary can)? Q6. Is there a situation where Mary can see her own files but not create folders there? Q7. Can you list the Win permissions for us for a standard user (ie what can and can't a user view)? Q8. Could you explain a little more about how permissions work in Windows from Win98 and up? Background: We want to create _our own_ image thumbnails programmatically regardless of the file location. But we DON'T want (1) to mess up the folders with lots of thumbnail files or folders (2) Mary to be able to view thumbnails of images she can't view (eg by Fred creating a thumbnail of a file Mary can't see and putting it in a place she can see it) (3) duplicate the thumbnail DB for multiple users. **Ideally the thumbnails would live in a duplicate folder structure in Docs & Settings/All users - but with the appropriate permissions. However, perhaps we could live with a 'Thumbnails' folder at the root of each structure of fixed 'permission'?** Q10. Can you think of any other way of achieving the aims? Q11. If the 'folder at each root' idea is the only workable one how do we programmatically find these roots? ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Win98 and up