>I have a FoxPro 2.6 application that the client wants to port without a complete re-write to VFP 6.0.
>Do you know if that is possible?
>If yes, do you suggest any tool to use or methods to follow.
>Also, are there any sensitive areas that I should be careful about or aware of during or after the porting process (if the latter is possible)?
>
>Thanks for your response.

1. menus - if you used system-like menus, just reuse them, else write from scratch.
2. reports - the converter just does a pretty good job; I had to tweak it some to take some other font as default and to take my cinemascope reports into a condensed font (used Arial narrow) so it would fit on a A6 page portrait.
3. screens - don't use the converter which comes with VFP. It will create some half-girl-half-fish screens that are neither screens nor regular OOP forms. If you're converting from DOS, use the converter by Alejandro Sosa (first version is somewhere in the Files section, and the new version may already be there). It will create regular forms which should look nice and behave as they should, and mostly do the rewrite for you.
4. other code - you may want to move the code into small modal forms. I know I had lots of those, for processing and reporting, and the best way I found was to turn them inside out - they used to be relatively long procedures which had small modal screens embedded; now that's small modal forms with most of the old code stuffed into click methods of a few commandbuttons. Had to do a lot of replacing of things like _SomeVariable with ThisForm.SomeControl.Value throughout the code, but once you do that, it's a breeze. It's actually the tweaking of this code that takes your time, but it's shorter than rewrite from scratch.