forums.silverfrost.com

[Clay]

I have an executable that, when installed in Windows, resides in C:\Program Files (x86)\ProgramName\. I've got data files in the install folder which are opened and read at run time. I open the files using a FTN95 "open" statement with the file designated by a text string beginning with "C:\Program Files (x86)\ProgramName\".

What some of our customers have found is that sometimes Windows makes copies of the data files and stashes them in C:\Users\[USER NAME]\AppData\Local\VirtualStore\Program Files (x86)\ProgramName\. What's worse is that when users install updated versions of our program, Windows doesn't update the Virtual Store copies of the data files with the consequence that my executable is opening and using out of date data files. This even though the updated data file is sitting right next to the executable in the install folder and I'm using a file address string pointing at the right file.

What's going on? Is there some syntax I can use for the "open" statement or some other trick to let Windows know that I want to open the file I asked for not a copy of the file stashed in VirtualStore?

Thanks in advance for any comments or advice.
Clay

[wahorger]

It sounds like your installer has an issue of where precisely to store these files. There are "rules" that define where certain things are installed based on which version of the OS under which you installed.

My deployment builder (DeployMaster) help file specifically calls out the change in installation of certain User files from the "Program Files" folder to the "User" folder, similar to what you are referring to.

The text in their Help file says:

[Clay]

Thank you wahorger.

Forgot to mention that these are ReadOnly data files which are stored in C:\Program Files (x86)\. The files are just databases which I need to use to retrieve values from time to time.

I'll look in the installer Help to see if I can find a hint...

[JohnCampbell]

You may want to look at
http://forums.silverfrost.com/viewtopic.php?t=2465&start=60

The problem looks as if you are sometimes opening the files for writing, but do not have the permission for this action.

Could you try using C:\ProgramData\ProgramName\... for your files ?
I have not tried this but it looks as if this is an area provided for this purpose and may have different protection.

Years ago, I had given up trying to solve this problem on Windows 7 and created my own area c:\utils to store files. I probably should have tried C:\ProgramData\ProgramName if it works.

Let us know how you go

John

[Clay]

Good idea John.

When the problem first started happening I went through all of the source code and did find a few "open" statements that didn't have "action= 'read'", so even though I was using the file as read-only maybe Windows reserved the ability to read-write by making a copy.

I never noticed the ProgramData folder before, but that may be a winner!

Clay

[wahorger]

Your installer might be able to set the default permissions on the folder and/or files for you as well.