It's known bug/feature. See Message #547633

>I just recompiled and rebuilt my WebConnection application with VFP7 and wanted to implement it on our webservers. I tried using the Install Shield program to make just a VFP7 runtime setup for the exe I built. Followed instructions from the deployment white paper, read helpful hints from posts here. Ran my setup program as administrator, then logged in as a normal user and got "VFP7 runtime library not found". Checked that all the runtime files were installed, etc. OK, I thought, must be my fault, did something wrong. I downloaded the updated runtimes from the MS site and ran that setup: same result. Registered DLLs manually: Same result. Finally gave up and copied the VFP7 runtimes to the application directory and registered: It worked!
>So my question is did I miss something?
>ISE merge modules copy VFP7 runtimes to C:\Program Files\Common Files\Microsoft Shared\VFP\ but that directory doesn't seem to be in the DOS path for normal users.
>The HELP file says for the BUILD command: An executable file created with BUILD EXE requires two support files: Vfp7r.dll and Vfp7renu.dll (enu denotes the English version). These files must be placed in the same directory as the executable file or along the MS-DOS path.
>
>The HELP file says for VFP7r.dll: The in-process .dll first called has exclusive use of the vfp7r.dll run-time library (typically installed in the System folder or the System32 folder, depending on your operating system).
>
>The HELP file says for Visual Foxpro run time libraries: Note As with all Visual FoxPro run-time files, these files are also installed in the Windows System folder.
>
>Is the merge module for VFP7 runtimes installing them in the wrong directory?