Bryon - I have upgraded several 2.x projects over the years. Some were conversions, some rewrites. So here's my 2 cents worth as they apply to your issues.

>The code will have a 6+ year life cycle...
Any project that has that much time left should be rewritten. Customer expectations for software will continue to change over the next years and it is very hard to make 2.x applications work like newer Windows apps. You should see some of the code I wrote into a FPW2.x app that had to run in Windows 3.1 to make it behave like a 32-bit app. Your customers will expect the application to keep up the times.

>...will have minor modifications for each customer.
Well written object oriented apps are much easier to customize and maintain for individual customers. This will save many programming dollars over the 6+ years of it's life.

>The spec is to directly convert the data tables
While VFP can read and write FoxPro 2.x tables, you will lose considerable functionality. Changing to a VFP database is pretty painless and opens the door to a lot of database power.

In summary, while the quick conversion looks tempting, for a project with this much life ahead of it, it could prove a costly mistake.

David Fluker.



>Please respond to this message if you have an opinion on the issue.
>
>I am being nuetral on my presentation of the facts, but I really need a massive industry consensus on the pros, cons and overall viability of this approach so that I can present management with more than just my opinion.
>
>Thank you.
>
>
>
>
>My company is going to hire a consulting firm to upgrade our current FoxPro 2.6 code to FoxPro 6.0.
>
>The spec is to directly convert the data tables, ~20 screens and 10,000 lines of code in .prg files. Approximately 95% of the code should be directly convertable.
>
>This is a high level concept of converting from Foxpro 2.6 to FoxPro 6. I need an industry consensus on the pro's and con's of a minimal conversion upgrade versus a major rewrite.
>
>The code will have a 6+ year life cycle, and will have minor modifications for each customer.