If you didn't just cope a folder, but installed an app, yes, dan is totally right, that setup would naturally install the runtimes somewhere.
I disagree somewhat, that the application folder is not the recommended place for the runtimmes. What's true is, that VFP documentation recommends installing into system folders, so the runtime is shared. The problem with that is, when you deinstall you can't remove runtimes, because there could be secondary vfp applications. Also there are at least 3 vfp9r.dll, all with that name, and unlike the global asssembly cache the system32 or syswow64 or microsoft shared\vfp folder can only hold one of them, not all sp and hotfix variants.
For that reason and again officially from MS there is the rule against DLL hell to put DLLs to an EXE, because the hell is not many copies of a DLL in many application folders, but a central DLL which should exist in several versions but can't and which has no responsible application for it. It's a good thing to do in a company knowing it'll only need one SP version for any major VFP version used throughout the company. That's one situation I have.
Anyway, a setup can install somewhere else, the runtimes can be registered and it will be available for apps without sitting side by side with them. There are VFP runtime installers that also register the DLLs. Not because the ISP doing them wasn't aware of the better recommendation, but because a general runtime installer can't know where applications needing the runtime are installed, it therefore installs using the recommended central system folders.
Bye, Olaf.