>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.

>>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?

I'd also suggest Alejandro Sosa and his converter (it's in the Files here). It does a full conversion of SCX files - not the READ emulation; the resulting forms are fullblown VFP forms, code snippets become methods (or remain as routines in the .spr file which is used to have the Do Form command in it). Humberto may try it on couple of forms before deciding upon a rewrite, or use them as a starting point for the actual rewrite.