Foxpro Distribution Kit Manual
I have a requirement to upgrade a large multi-user application from FP2.6 to VFP9. I appear to have all source components (Programs, screens, menus etc) and.EXE file that appears to have been developed under the FP Distribution toolset. Unfortunately the original development machine has disappeared along with all manuals, software diskettes etc. Can anyone advise me how easy it would be to upgrade to VFP9 and point out any pitfalls I might encounter along such a course of action?I have also noticed some talk of a VFP9 DECOMPILER, is this a tool that can be used against an original.EXE file so that I can compare the source I have with that which is used by the.EXE module? I wouldn't go that route. Many (most) of use old-timers have done several conversions from FP to VFP years ago.
The consensus, by far, is not to do a conversion but to rewrite the program completely. It is a huge leap in software development technologies from FPW2.6 to VFP9 (or any version of VFP for that matter)You wil find that he biggest changes are in OOP, and the use of forms vs the old screens.I can tell you now that if you use any automated converter tool you will not be happy with the results. Screens will mostly work but will look more than ugly. This is the time to re-architect the program as a 3-Tier (maybe web-enable if you need that) object oriented program.The business rules and the code that enforces it can probably be saved and reused as it will be mostly compatible with VFP. The rest should be re-designed an rewritten from scratch.
I know it is not what a client wants to hear, but take the advice from the old timers that have been there many times. Since you appear to have all the source code, you can do a fairly easy test, as follows:In Windows:0) Make a copy of the entire development tree.In VFP 9:1) CD 2) MODIFY PROJECT?, then choose the project file that seems to represent your application.3) You'll be prompted to convert the application from FP2.x to VFP format. Choose Visual Conversion to create a runnable application.4) When the conversion is done, find the main program (it'll be shown in bold). Modify that main program and add this line near the top:SCREEN.Themes =.F.Then, resave it.5) Click the Build button and choose BUILD EXE.If the project compiles without error, you're way ahead of the game. In that case, try running the EXE and see what the results look like. Chances are you'll think it's way too ugly to use.If the project doesn't compile, come back here and we'll help you fix the errors that are keeping it from compiling, so you can finish this experiment.Tamar. I wouldn't go that route.
Many (most) of use old-timers have done several conversions from FP to VFP years ago. The consensus, by far, is not to do a conversion but to rewrite the program completely.
Foxpro Distribution Kit Manual Pdf
It is a huge leap in software development technologies from FPW2.6 to VFP9 (or any version of VFP for that matter)You wil find that he biggest changes are in OOP, and the use of forms vs the old screens.I can tell you now that if you use any automated converter tool you will not be happy with the results. Screens will mostly work but will look more than ugly. This is the time to re-architect the program as a 3-Tier (maybe web-enable if you need that) object oriented program.The business rules and the code that enforces it can probably be saved and reused as it will be mostly compatible with VFP. The rest should be re-designed an rewritten from scratch. I know it is not what a client wants to hear, but take the advice from the old timers that have been there many times. Since you appear to have all the source code, you can do a fairly easy test, as follows:In Windows:0) Make a copy of the entire development tree.In VFP 9:1) CD 2) MODIFY PROJECT?, then choose the project file that seems to represent your application.3) You'll be prompted to convert the application from FP2.x to VFP format. Choose Visual Conversion to create a runnable application.4) When the conversion is done, find the main program (it'll be shown in bold).
Modify that main program and add this line near the top:SCREEN.Themes =.F.Then, resave it.5) Click the Build button and choose BUILD EXE.If the project compiles without error, you're way ahead of the game. In that case, try running the EXE and see what the results look like. Chances are you'll think it's way too ugly to use.If the project doesn't compile, come back here and we'll help you fix the errors that are keeping it from compiling, so you can finish this experiment.Tamar. My client has decided to limp along on the existing software developed under FP 2.6 but needs a few changes to it and all the old manulas/diskettes have been thrown out/destroyed. I have sourced a:FoxPro 2.60 Prof. For Windows, 3.5'$595Yes, disks and manuals only. Missing Graph, Help Compiler, Lib.
Construction and Connectivity Kit manuals. No box, license agreement card or reg. Distribution Kit manual is included in this packageon the web. I am just a little concerned that I might not be able to install this on a modern laptop/desktop.