Visual Foxpro 9 Runtime Files
How do you know the runtimes aren't installed? They are unlikely to be in the same directory as the.EXE I suspect they are in the Programs Files(x86) directory.Having 2.exe files that do different things on the same tables is a little unusual, but not at all out of the realm of possibility. Sometimes maintenance programs are done separately.You don't mention what the.EXE's do.
It could even be an old version, vs. New version and someone didn't delete the old version.Best Regards,ScottATS, CDCE, CTIA, CTDC'Everything should be made as simple as possible, and no simpler.' RE: vfp9 app.exe including runetime files (Programmer) 16 Aug 15 17:01. If VFP9 runtimes are installed outside the application folder the runtimes need to be registered to be found and then can be found by searching the registry (well, that is how the EXE stub code looking for the runtime finds it).You can also find out the vfp version of an exe by opening it in a hexeditor, you'll somewhere find 'VFPRuntime.9' - Don't remember the exact string, but it should be somewhere at the beginning or end of the whole EXE file.Bye, Olaf.RE: vfp9 app.exe including runetime files (Programmer) 16 Aug 15 18:49. If you don't find some string like VFPRuntime.9, it's not a foxpro application. It could be.NET or C or anything already finding runtimes of the language it needs in the OS systems folders.There is no way to compile a VFP.EXE having included it's own Runtime, the only halfway possible thing I can think about are tools like KONXISE creating a self extracable EXE of a encrypted VFP application, maybe also including the runtimes. Echometer model d manual muscle. VFP is no linker, it does not link DLLs nor LIBs into one standalone EXE but there are ways like the self extracting archive.
In the end it'll put runtimes on hdd at runtime.Bye, Olaf. RE: vfp9 app.exe including runetime files (Programmer) 18 Aug 15 02:25. 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.
Visual Foxpro 9 Download Full Version
Also there are at least 3 vfp9r.dll, all with that name, and unlike the global asssembly cache the system32 or syswow64 or microsoft sharedvfp 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.RE: vfp9 app.exe including runetime files (Programmer) 18 Aug 15 09:25.