I do agree completely with your statement, however there is a way around this (at least something that has worked for me). It's not the most "robust" solution, but It did work in a test environment.

I basically locked down the folder structure how I wanted it. I then made a "folderadmin" username that had pretty much full control over the folder structure. Now, in my environment we have the server mapped to a local drive - and I'm sure this is very common for many people. When mapping the drive I use a UNC (also like normal). In my code, when I wanted the give access control of the folders I would use VBA to create ANOTHER mapped drive except using the IP address of the server. I would make the changes to the folder structure and unmap the drive (the IP one) in one function.

So this allowed me to lock down the folder structure yet give access to the Access DB for a very short amount of time when modifications were needed.

So like I said in the beginning - I didn't consider this a "robust" solution as I have not tested it in a large, uncontrolled environment - but it did work quite well for all of my testing.

I guess the question to you, Richard would be do you see any major pit-falls to this method? The major ones I can see is if the application happened to crash when it was mid folder change, the user would be left with two mapped drives - one with limited access and one with basically admin access. The only way I can think to help alleviate this would be to "hide" the mapped drive, but I have not done the research to see if this is even possible. I don't know, your thoughts and criticism is very much welcome.

Thanks and love the classes!

Derek

---

Reply from Richard Rost:

That sounds like a very unique solution. I wouldn't have thought of that. If you're temporarily mapping a drive letter and then releasing it, it wouldn't matter if you used the UNC or the IP address - the result would be the same. It would take a PRETTY savvy user to figure out what you're doing and hack that.