Wouldn't a language translator be great? When learning a new language, the biggest hill to climb IMHO is the syntax. It would be great to type in my VFP code and see the VB or C# translation! I would learn the new language so much quicker! Once I see a 'visual' representation of what i need to do, I remember it. Took me awhile to learn Delphi even though I had learned pascal YEARS AGO. Just couldn't get used to putting a ; at the end of every line! :0)

Tracy

>Thomas..
>
>IMO, VFP 8 should be the last major version... After that, 2 years of support with service packs in the same manner VB is supported...
>
>As for where VFP developers will go, MS's biggest fear is that they will go somewhere outside of MS. Personally, I think this fear is unfounded. A lot of people talk about Java, but when push comes to shove, there is no better fit for VFP developers than VB - whether it is VB 6 or VB .NET. Some will say C# is a better fit because of its structure. It is a moot point since 80% of what you do in VS .NET is with the framework - which exists apart from an implementing language.
>
>With this in mind, IMO, the best thing MS can do for the VFP community is to put a certain amount of clarity and finality in the mix. Make it clear that the next version of VFP is it. Make it clear that .NET is the future. Make the path to migrate as clear as possible. In the end, you retain a loyal customer base that will will help stimulate the beginnings of a .NET developer community.
>
>Of course, what do I know about strategy??? I have been accused of not being a strategic thinker...< bg >...
>
>
>Regards,