FoxPro 2.6 is a VERY stable development environment.
Would recommend you go straight to 2.6a with the fast machine patch if you are working with PC clock speed over 300MHz.

2.6a: http://support.microsoft.com/support/kb/articles/Q102/8/93.asp
"Fast Computers" patch (courtesy Bridget Cronk, yesterday): http://support.microsoft.com/support/kb/articles/q240/9/82.asp


>Hi Evan
>
>Main aim of the convertion is to give Windows interface feeling to the software so that we can call it as ' Windows version '
>
>How stable is Foxpro for Windows 2.6. It's packaged software & we sell at other cities through our Dealers.
>
>Another constraint is time. We would like to have a Windows version at the earliest. Another factor is cost. We would like to sell the software at the same cost as DOS version & phase out DOS version. A re-write in VFP might involve more time than conversion.
>
>A fresh, starting from scratch VFP version with OOP's programming will also be started later.
>
>Rakesh
>
>
>
>>Hi Rakesh.
>>
>>My opinion is to not attempt a conversion of the program, but instead rewrite it. Here are my reasons:
>>- the conversion is rarely smooth, you will need to tweak it alot to get it working and looking good
>>- if you convert you will have a slow (user interface wise) verion of your old program that has no added functionality. So in essence you have made your program worse
>>- why move to VFP if you aren't going to take advantage of its features
>>- forms converted from FPD are almost impossible to maintain because they contain a lot of code and pageframes to make everything work in VFP
>>- you will not learn how program in VFP properly since you will still be using the old FPD techniques in your application
>>- it is difficult to integrate new forms into an app that has converted forms
>>- your learning curve for VFP will be lengthened
>>
>>I have formed these opinions from converting a major FPD app to VFP3. My learning curve of VFP was stretched from 2 or 3 months to almost a year. It took almost 1.5 years to remove the last bits of old code from the system.
>>
>>As far as I know there are no books on the topic. Check the VFP help for some strategies.
>>
>>Other people have other opinions on this topic.
>>
>>>We have a large Accounting sotware written in FPD 2.6. Now we would like to convert to VFP 6.0. We are NOT planning a rewrite because we would be starting Fresh with OOPs progamming with more features later on. At present would to like to just convert to VFP with the same code.
>>>
>>>Please suggest
>>>
>>>1. Migration Strategy.
>>>2. Good books ( OOPs is not a requirement )