Well, rather install VFP in C:\Users\Public or grant write access into at least ffc subfolder of VFP. VFP wasn't designed for UAC and restrictions and redirections of file writes into virtual store and of registry writes into eg Wow6432Node. In XP you could also write into Program Files folder as member of some local user groups, main computer users AFAIR, not only as admin. Today Admins also don't inject their elevated permissions into all processes they start, so it's not a major solution to run VFP as admin. In an ideal world the VFP installation would install its samples and foxpro foundation classes and all "movable" parts into application data.
The simplest solution, if you have installed in the default restricted program files folder is expand permissions for that folder, not run VFP as admin. Because once you run a process (vfp9.exe) elevated, you can do much more than what you want to grant it. The problem also only starts with two users using VFP, as redirection then is only one-and-a-half way reflecting back, every user has his own VirtualStore folder within his profile and that's what mainly causes this error, first user using wizbtns recompiled it and caused vct to be stored in his profile, the next user has a discrepancy.
Another good option is to not work with the recompile all files switch in build. This way you don't let VFP compile FFC classes and use them as is, they come precompiled anyway.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.