>Initially, I would agree with you. There would be plenty of jobs for us for
>the first few years. (Actually, I develop apps for the company I work for
>so I wouldn't be competing with you for the job market.) But after that, I
>think the story would change. The problem with your scenario is that it
>doesn't account for changes in technology. If VFP gets killed, what happens
>when the 64-bit chips and OSs come out? That's not too far off in the
>future. If there's no 64-bit version of VFP, companies will eventually want
>their apps ported to something which can take advantage of new
>technological developments.
>

Gary,

You are correct, at some point in the future there may not be a VFP, so what? I have to make business plans for myself, I make those plans for a period of 2 - 3 years at a time. Right now, VFP is fine for the next 2 - 3 years. Next year it is time to read the writing on the wall again.

If you really want to here what Microsoft is saying is the direction of things to come, it is component development. That means using more than one tool to build and application. This does not indicate that VFP is dead, but it does indicate that building monolithic applications with a single development tool is dying.

So we start learning new tools, stop comparing them to our precious VFP, and get on with it. Use the best tool for the task at hand.