>>>
>>>Some argue that they are afraid that their application will nor work in newer versions. The compatibility history of VFP is unique, personally I have never used more than a few hours to get my application to work in a new version. And most of the changes I have been forced to do, have been to fix my own typos, because newer versions have more strict syntax checking.
>>
>>In way you express it, I agree with you. As a developer I too like to have the best tools at my disposal. But from time to time I come across a client that don't want to risk the upgrading.
>
>Does your client still drive a T-Ford because he did not risk the upgrading? :-))

Good one.

>
>The thing is, as I see it, that since most other programs have only limited "downwards" compatibilty, people simply will not trust that VFP can have it. The last years this compatibility "hell" has become even worse, in people's mind, because they heard about the close to zero compatibility that exists between VB6 and VB.NET. And also between the different generations of dotnet the compatility is a big issue.

Even though my knowledge of the .NET language is limited, I have notice (and heard from other) a lack of backwards compatibility across the version of .NET languages. Last year a company I work with spend several month twiking an ASP.NET writen in version 1.1 to get it to successfully compile and run in .NET version 2.0. It is these problem that make me to continue to like VFP.