Any IDE just manages source code and results in compiled object code, eg a DLL, OCX or an EXE. NET Framework in the aspect of the runtime. Then an EXE can work, but you simply start the EXE, not try to open it in Foxpro. The Foxpro Version you install, because a Foxpro installation also installs the Foxpro runtimes. But installing Foxpro does not help you with an EXE not working, unless it's built in You can't open a EXE built by Foxpro in Foxpro, you need source code files, a PJX is typically the entry point into a project with all it's code, forms, reports etc. or older foxpro applications.ġ.1 Foxpro itself and the foxpro language are downward compatible, but compiled versions need their right runtime.Ģ. The latest Runtime is the VFP9 SP2 runtime, but this runtime doesn't run VFP8,7,6. If you don't find it, it's either not a VFP exe- I'd guess, then it's even a VFP DOS EXE.ġ. Next thing after that text is the foxpro version. Search for " FoxProRunTime"Īnd notepad will move there. Don't touch anything,at least don't save after editing. Windows Explorer to change the file extension to TXT to let it open in notepad. Really right click on the EXE and choose Edit with notepad. Well, the solution is quite obvious, isn't it? Once you know the foxpro version an EXE is compiled in, you can install the appropriate VFP runtime version.
0 kommentar(er)
