>Actually in a roundabout way, you've hit the nail on the head. By virtue of the fact that I could install and use FPW2.6 and still be productive, the ongoing development and release of new versions of VFP is almost self-limiting. There are many developers out there who are working with clients who don't have the latest hardware still and will always be behind the leaders in adopting such technology. Microsoft are busy pushing .Net but they don't mention that to use a .Net app effectively you need a pretty powerful PC. If you put someone who knows VB.Net or C# in front of a PC from 10 years ago, gave them a copy of VB4 or C and told them to write an identical app they would be in big trouble. But a FoxPro programmer could do that and be productive.

I understand your point completely as I understand the Latin Amercian market (and I would then assume many other developing countries share similar issues), that not all hardware is up to date. It is one thing to try to sell .Net to the enterprise. It is another to go with a .Net solutioon to your small client with say, 10 PCs and tell them that on top of your fees for creating new software they have to upgrade their hardware. That is an extra cost layer that will probably break the deal.

I am not saying that VFP developers should stay with older versions and that we should not learn new technologies but that VFP is a viable solution and also backward compatible and that is a great asset in many markets. .Net cannot say the same.