Question : Conversion from FoxPro 2.6 to Visual FoxPro 9
I am working with a FoxPro 2.6 system using both Windows 98 and DOS. I have been working with the Visual FoxPro9.0 Beta to test my code to see if it will run under the new version. I have been able to get the code to run with the new version using the full installation of the VFP Software on a development machine.
My question is this: How do I go about compiling the code into executables that can run on client computers that do not have the VFP9 installed on them?
My current setup is this: FoxPro 2.6 and FoxPro for Windows 2.6 are installed on a server. All of the clients access the FOXPRO.EXE and FOXPROW.EXE files on the server and run them locally. All database files (.DBF) sit on the server.
Do I now compile all of my .PRG and other files into some sort of an APPLICATION file that I can place on each end users desktop? That is what I have done in the past with MS Access. This way, every desktop does not need a License for VFP, but just Windows with a compiled application.
Do I have this right? I’d like to know that I am working in the right direction before I plunk down the money to buy the new version.
Solution: Conversion from FoxPro 2.6 to Visual FoxPro 9
If I understand correctly, all of the current applications are just prgs and sprs ..ect and the users are running them by launching foxpro or foxprow and the something like typing “DO myprg” in the command window ?
What you need is to build a “Main” prg, have it provide a window or a main screen or something to launch all of the other prgs, spr’s etc. Then build a project by putting that ‘main’ prg in it and letting the project manager go find all of the other prgs, then you build an exe from project. Most people will copy the vfp runtime dll’s to the local PC’s and register them.
Go to the command window and type in HELP building applications