Exactly. As much as I want VFP to be improved, I have to realize that one day it will not make good business sense for MSFT to do so (if that day has not already arrived). However, with all of the fantastic features and capabilities of dotnet, until it ALSO performs as well as VFP does in data munging, I will continue to work with VFP. That is, until it no longer exists or is no longer supported, or no longer meets our needs. I only hope that dotnet gets 'there' before VFP is no longer a viable tool.


>>When you don't have to worry about money anylonger, the only thing that matters is your reputation. There is no way dotnet will not succeed (no matter how much $ MSFT has to throw at it). To be fair, their longterm vision is a good one - it is the painful process of getting there that is the problem.
>
>Thank god VFP is there in the meantime. I mean I don't need .Net so I can keep making pretty good apps until THE DAY comes I can't work anymore without using .Net
>
>
>And when that day comes they will probably have :
>
>- added a local cursor in .Net
>- added new tools that will let us be a lot more productive and write less code
>
>I feel the pain and frustration of those that loved to work with the fox but can't anymore and are forced to use .Net because of the suits.
>
>Those developer's frustrations are there because some of us are lucky enough to be able to still make a living with the Fox. Perhaps we'll win both ways. We'll continue to use the Fox for a while and during that time they are forced to write gazillion line of code and they know that they're writing those lines because the REAL tools are not there yet.
>
>

>Here's the cycle:
>
>1. They write too many lines of code
>2. They complain because they did'nt have to lose their time on that before
>3. MS reacts by providing more tools to automate that code creation
>4. There are some things that could be better. That used to be easier with tools like Fox ,Delphi or VB.
>5. MS reacts by providing more tools, add stuff to the framework to automate that code creation
>6. Did the product evolved in major ways?
>7.   Yes: Release a new major version of .Net
>8.        Go to step 4
>9.   No : Go to step 4
>