I do not mean to scare you from vfp 5.0, but I have been working on a 2.6 to 5.0 conversion since June 1998. For the first 4 months we had 3 programmers, now it is just me. I have about 3 more months to go.

We originally converted because our 2.6 app would not run on machines faster than p166. Ours is a banking application for lending on commercial real estate. Fairly complicated, but not rocket science. There are about 100 screens, 150 programs, and several hundred reports.

Converting from 2.6 to 5.0 is not a simple task. You can not just compile under 5.0. 5.0 will convert your 2.6 forms. The form converter does the best it can, but your app will not run cleanly after the conversion. And your app will not really be 5.0, it will be 5.0 converted from 2.6. The converted 2.6 code has its own unique methods and properties, that are not found in new 5.0 apps. The report convertor does a better job, if you can get it to run (I had a problem with "bad parameters" in the report convertor. Most people do not have a problem with the report convertor. Guess I was special.)

You will almost certainly have to rewrite the main part of your system if you choose to go to 5.0. It just does not make any sense to go to 5.0 and leave the code in converted from 2.6. You gain nothing but headaches. There are 100 million little differences. Why take that on just to be 5.0? Also, before we decided to rewrite our major screens, we had problems using any of the newer features: toolbars, pageframes, grids, toplevel forms, etc. We did leave the popup, additional information forms (the modal forms) in converted 2.6.

Last bit. If you decide to take this on, get someone who is experienced in converting from 2.6 to 5.0. And get someone who does not voice an absolute opinon that "it must be rewritten totally to 5.0" before they even see the app. Consultants that do not have experience in a conversion, of course just want to rewritew. As I said, we left many of our modal screen in converted 2.6, with no problem. But you do want someone that knows vfp 5.0 to set you up with a good framework to start. It is important to start with a good application foundation before starting to rewrite any of your 2.6 forms.

Good Luck - Brenda

You ca

>We have a need to carry our foxpro 2.6 for windows application to Visual Foxpro 5.0. How many work will we take to do it, if the foxpro 2.6 project has 115 screens and the same number of reports, aprox.
Can I measure the time or the effort we need? Maybe could we generate an EXE in VFP 5.0 without convert source code, as a beginnig? What is the main advantages we will have?

>Thank's