>>Having to retool and rewrite with technology advances is what keeps most of us in business. Do you use a rotary phone and a party line or have you progressed every few years with everyone else and had to relearn and reload a new phone?
>
>That is the dumbest comment I've read in this post. When you change phones, you simply go out and buy a new one start using it. Perhaps you are somewhat handicapped when it comes to changing phones.
>
>How can you compare that to the re-writing an application that has taken 3 or 4 years to write and may take 3 or 4 years to convert, not counting the time it takes to learn the new development language?
>
>Besides, I thought I was keeping up by upgrading to each new version of VFP whenever they came out. It is my opinion that what MS has done is almost criminal and I don't associate with criminals.

Without characterizing your comments as "smart" or "dumb", I have a couple of questions :

Is it really being suggested you rewrite a successful application just to say it is written in .NET?

When you began development of an app in VFP 3 or 4 years ago (as did I) and granted that it may have been absolutely the best choice of tool at the time for what you wanted to do, did you really have no idea of what Microsoft was planning for the future?

The last version of VFP was released 5 years ago. Did you really think that by upgrading to vfp 9 you were "keeping up" in the larger sense ?

I love VFP, I am still using VFP, I have made a lot of money with VFP and if they had put the resources into VFP they put into .NET I could by an island on training revenue alone - BUT

whatever the technical arguments or personal pain or complete contempt for decisions MS made that were not in your or my best interests : Did you really not anticipate the present situation three or four years ago?