>>>>Solve the problem.
>>>
>>>I did. Switched to Linux five years ago :).
>>>
>>>> It's solvable the right way since, what, W2K? 21 odd years?
>>>
>>>If so, how do you explain that the solution is not widely known, but instead, among the 60 of us regulars here, the question occurs 3-4 times a year? Even better, if there's a solution since 20 years ago, why is the problem still there in each new version, and solution is not?
>>>
>>>Just for curiosity's sake, what's the right way, why is it right, and why is the above wrong?
>>
>>Calm down boy! The better question is Why is there Not a Q/A section, were someone (like me) would have found the Answer with instructions on how to solve the issue. So far, this site has been a excellent place to pick minds about VFP issues. There may be other sites, but they then to respond to my question with a "That question has been ask before", without providing a link to the solution.
>
>I'm not complaining about the FAQ existing here or not, I'm complaining about this still being an issue when it's something "solvable the right way since, what, W2K? 21 odd years?". If it's so simple, why is the solution for it not in them windowses since XP?

The problem is in VFP, not in Windows. VFP was crappy transformed to Windows from the start (storing data to Programs folder was wrong in Win95, while not discouraged from the OS by keeping compatibility). And later on it was not fixed, the old tools where just kept. So do not blame the OS. While not the best possible OS, Windows is completely fine here.
Since VFP tools are under useres control, the problem is on user side. Installing wrong place, running as admin, setting inappropriate access rights, name it. instead of thinking through the problem. It's not that hard to fix.