VFP 3 will try to upgrade from either 2.6 or 2.5, but... IMHO, it is not worth it to try either upgrade process. Generally, when you upgrade, you have to choose between the look and the functionality. Either way, you get a bunch of extra crap that you would not have otherwise put in if you had written it.
I agree with George, you are better off taking the 2.5 version and rewriting it in VFP3.
BTW, you can actually run the FPD2.5 program as is in VFP3 and upgrade the pieces to obj oriented as you get to them. Whether or not that is worth it is really situational.
Any time I have done it though, I have found the only real way to do it is to make a feature list of the old code, really go though it well, then rewritting the whole thing(cutting and pasteing code where reasonable).

HTH
Bill

>Hi John,
>I can't answer your main question, I forget what versions VFP 3 will 'automatically' upgrade. Unfortunately, using any of the auto upgrade features do not work exactly as many of us would like. I have tried going from FPW 2.6 to VFP 5 for one fair sized application. Due to all of the quirks that I ran into I finally gave up and decided to rewrite the entire thing.
>

---

>>Hi all,
>>
>>I've got an old system that was written in FPD 2.5. Some screen sets are used, but much of it was written longhand. I'd like to bring this up to Visual 3.0. Would you suggest I go through Win 2.6 first, and then go from Win 2.6 to Visual 3.0, or could I go straight from 2.5 to Visual without too many hassles?
>>
>>Thanks much,
>>
>>John