David-

You may want to try the old "AppDev" migration method. This would allow you to execute the FPDOS .SPR files instead of going the converter route. The Converter was a good "idea." The problem was, it never really worked well and most people who wanted to get on with VFP ended up reworking everything in an OOP environment.

Their methodology is probably still on the AppDev website. However, it basically says to open a new project, import your main program and rebuild the project. You will then bring in the .spr files for the screens (generate them in FPDOS if you don't have .spr files). The reports should not be an issue. You don't have to convert them (they just won't be Windows-like until you do). You can then convert the screens yourself in an orderly process. Any screen changes to unconverted screens can be done in FPDOS, .spr generated and then updated in the VFP project.

I had a large project that started in FoxBase and went through this process and it worked beautifully. The customer was delighted with the results and we kept on incrementally changing everything until it was fully converted. Actually the reason we started the entire conversion was to get rid of an old dot matrix printer and move the system over to laser printers. But the end result really worked out nicely.

--Steve.


>I have an application that has 261 screen files and 193 report files in FPD 2.5b format. I want to convert them to VFP 7 format to save having to duplicate them from scratch.
>
>
>An error occurred in the Converter and it cannot continue. The error has been logged in d:\testdir\error99.log. Open the log file?
>