Hi Tiemo,

What you observe is normal, expected behaviour. As an administrator, you can put files that have to be available to all users into drive: \documents and settings\all users\application data\... For example during installation. Users without admin rights can save preferences files in drive:\documents and settings\ username\application data\... I'd use two different files, one in ...\all users\... and another one in ...\username\... for different purposes.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum

We are always looking for new projects! Feel free to contact us to discuss your custom software project!

On 7 jan 2009, at 18:08, Tiemo Hollmann TB wrote:

Hello,

For the rare windows guys...

I want to save an ini file for my app in the specialfolderpath(35), which is \allusers\programdata\... so that every user has access to the same ini
file.

When checking the privileges a standard domain user has no writing
permission to that dir, but when testing I can create and write to that dir
- first hmm?

But if I first sign on with a user who has admin rights and I create my ini file in that dir, afterwords the standard user can't write to that ini file
- access forbidden, second hmmm?

Now I could tell my customers, they have to change the permissions to that dir or file for the standard domain user, but what I would like to know is, if this a standard configuration / behaviour, or if it is something in my special configuration or if there is a workaround so that every standard
user has access to my ini file. My thought was that the
\allusers\programdata\ path is accessible for all users. Ok it is, but not
for files created by other users. Hmm?

Thanks for any hints

Tiemo


_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to