giving the data files, made by app the secruity settings the same.

[ThEiMp]

Dear VBFormers,

I have found my problem in my encription techniques that i have adopted, like so. The reason that my app isn't being able to encript and also decript, is that it is looking for another login, on that i had removed from this system, that i am working on with it. So then if i use the "Everyone" secruity settings for my Built Project EXE and then i wish to have it so the same on the files, that i write with then so.

!! Thanks in advance !!
Richard Graeme Ambra

[wqweto]

Still looking for anyone to do more unpaid work for you???

cheers,
</wqw>

[ThEiMp]

for yeah sure, i am also doing that still, even so

[dilettante]

Most folders have security set up on them so that new folders and files created there inherit a default set of security attributes. Some of these can be complex, employing special security identity groups such as Creator Owner.

It can be a big topic, and a bit intimidating to users who rely on appcompat and admin account use to try to simulate the wild west that existed on insecure Win9x.

A quick hack that can simulate the wild west again in the post-XP era where things got locked down further might be to create data folders and files in the new (well, new in 2006) "Public" special folder.

This isn't designed to be a fixed path across Windows installations. The easiest way for your programs to locate this folder when they run is probably to interrogate the environment variable PUBLIC, as in:

MsgBox Environ("PUBLIC")

Or you can call SHGetKnownFolderPath(), etc. to look up FOLDERID_Public.

That's really meant to be a "root level" path, so your programs should probably check for (and if necessary create) a uniquely-named application data folder there and then create your files within that subfolder.

Those files should allow any operation by any logged on user: read, write, delete, modify, etc.

[ThEiMp]

-- Thanks for the Input$...