Sure, if that's the case just set permissions in the folder to `INTERACTIVE` with full access.

I do this too, for the same reasons actually now that I think about it, but you know you can move FoxCode to a different writable location.

For a dev environment (and especially FoxPro) it's just fine to change the permissions. The concern is more for applications that write into the install folder which is generally a bad idea.

What I do actually on my own machine:

I have a custom `Programs` folder where I install certain things that I need more access to because the application 'writes' into the install folders. Apps that config files that are writable for example etc. I then set the `Programs` folder and all of its subs to `INTERACTIVE` with full rights. These also happen to be applications that get installed onto most machines and don't fit the typical installer profiles (some custom apps and some apps that you can no longer find like an old WinZip packager etc.) That stuff is all self-contained and is copied to new machines as is. Useful for migration.

+++ Rick ---

>Normally, I would agree with this. But VFP, and it tools were designed at time when this was not an issue. For example, the Intelisense. There are many intellisense addons I like. But with the the Read-only access on the VFP, the FoxCode.dbf does not get updated, the features don't get added. I have seen this when using Thor also. It seems easier to bend Windows to the way VFP expects it to be, instead of banging head against the keyboard and trying to determine why WIndows is fighting me.
>
>Besides, I do not do any development in the Program Files folders. I have a C:\Projects for my development.
>
>Thank for sharing your wisdom.
>
>>Anything is `Program Files` is not writable by default by a non-admin user. The idea is that you can't change an installed application or add additional executable code to an installed application.
>>
>>You can change permissions on the folder to add `INTERACTIVE` or your specific user account to allow full access (or whatever permissions you need).
>>
>>Frankly there's no good reason you should write anything into the FoxPro installation folder.
>>
>>+++ Rick ---
>>
>>>Even thou I have done this before, by accident, but how do I make the "C:\Program File (x86)\Visual FoxPro 9" and sub-folders Read-write.
>>>
>>>I have tried change the Read-Only option in the folder's Properties dialog. It indicates that the R/O is Off, but the files remain still inaccessible for writing.
>>>I am thinking it may some kind of permission issue, but I rarely mess with that, so I reluctant to play around in that unless I have the proper instructions.
>>>
>>>FYI: I have Windows 10 Pro.
>>>Thank you, in advance.