Quote Originally Posted by Arjay View Post
There seems to be a disconnect here. You've already agreed that the ApplicationData directory is not locked down by the system admins, right? And since Windows allows programs to create files and directories underneath the ApplicationData directory, you are going to be good to go. There isn't any need to make this harder than it needs to be. IMO, prompting the user isn't a good solution because most users won't have any idea where to put these files and will become concerned when they see temporary files appear in their My Documents folders. Why not follow the Windows application compatibility guidelines and store the app data in the correct location?
I see what you are saying, I'll have to check out if I can save to the users new account documents and settings folder. I looked at one of those examples where the person's name changed and it wouldn't work with Environment.UserName. The person did not have anything in the new user account's documents and settings folder, although I did not try to save anything to it. However, I did take your advice and the files are stored in application data now. It is not putting anything in the My Documents folder it's just taking "C:\Documents and settings\jane.smith\My Documents" and turing it into "C:\Documents and Settings\jane.smith\Application Data\Program Name" by removing 'My Documents' and replacing it with 'Application Data\Program Name'.