>>Another thing to watch out for is the directory in which application has been installed (assuming that the tables are in the same path as the program) -- in particular if the program is installed in something like "c:\program files" or "c:\program files (x86)". Generally wasn't a problem back in the Windows XP/Server 2000 days, became a problem starting with Windows Vista/Server 2003 when access rules became enforced. This combined with the directory virtualization feature could result in a potential "gotcha" -- especially in a case where you've got multiple users that need to be accessing a common set of tables.
>
>On some fresh systems (new servers or my own W7 box) I often ran into a situation when I couldn't rename, delete or edit and save a simple textfile (and same goes for tables etc) that I just created, because it was readonly to me. I checked and I was the owner of both the file and the containing folder and actually few folder levels above. And the owner was supposed to have all the rights, right?
>
>Nope. I didn't. But I had the rights to give myself the rights, so I specifically added my username to the list of users granted full privileges on the folder, and then it all worked fine. It may sound stupid, and I did feel like an idiot each time I had to do that, but it worked every time.

I do remember the first time I'd deployed openmediavault I kept running into wonky rights issues. It appears that the out-of-box configuration is only meant to have very basic access policy -- you either hand access or not. Once you tried to fiddle with configuration that resembled group membership rules, things got wonky pretty quickly. Was eventually able to correct the problems by simply going "old school" and configuring the underlying Linux and Samba through more "traditional" means and forgo using the web-based managment system it used. I also had to use chown at the Linux level to make sure the ownership was correctly set.