>But the deal killer is autospanning and record oriented processing, isnt it? :)

The killer is about people who are barely able to understand the problems they are trying to solve and use 'new technology' as an excuse for their incompetence. VFP plays in a niche market and has some nice features that are lacking (or inferiour) from the alternative. VFP developers who use the tool to their advantage will always survive those with bare minimum development skills and ride the hype and argu that these kind of features are irrelevant just to justify their own choice.

Those people are not willing to listen to reason or fact. But hey, that's life.



>
>>I was dreaming what if...
>>
>>VFP developers would take a look at other Microsoft products and really understand them. They could see that much of what they want is there and they could stop dreaming and get to work.
>>
>>>I was dreaming what if...
>>>
>>>What if MS made and announced the decision to add to .NET the missing features that VFP developers want the most? Here is a small list. Feel free to add to it.
>>>
>>>1) Now that LINQ in on the way, it would be nice if .NET included an efficent (fast - Rushmore) standalone local data storage standard. Sort of like a DBF on steroids: 64 bit, with long column names (32 chars is enough for me), with indices, buffering and native data encription. Naturally, it could be SCANed, included in an exe file, accesed directly from Excel, etc.
>>>
>>>2) A "dynamic language mode" that allowed a command window with full language access during development. While they were at it, it allowed the creation and compilation of snippets at run time.
>>>
>>>I am sure there are more, but I am not familiar enough with .NET to know. With just those two I could become a VB.NET fan.