>If VFP dies (which I don't think will happen, and I hope it doesn't), I will pick another language. If this happens, I will be giving-up some good things and I will be gaining some good things...but the bottom-line is ME. Am I a good developer or not? Any bickering about languages and what is better and what will last doesn't matter...if one dies, it will not affect a good programmer for long.

Well said! I've been watching this thread since it started a while back, and this is the first REALLY significant thing I've seen posted. It's not the language that makes us all good developers, it's our skills and experience. I program in 2 languages mostly, VFP and VB. I also dabble in VC++ and Delphi. There are things I love about each of them. But its not any one language that makes me as good a developer as I am. Its my logical thinking. Its my experience with computers in general. Its my ability to understand a problem from the user's point of view and be able to think of ways to solve that problem with a computer. Not with a specific language, just in general how a computer would tackle that problem.

You have to choose the language that can best solve the users problem. If serious number crunching is needed, maybe Delphi or VC++ is the way to go. If mass amounts of data need to be stored/processed, maybe FoxPro is the way to go. If development time is a major issue and you're not dealing with massive amounts of data, maybe Visual Basic is the way to go. Maybe you need a little of them all. Nothing's preventing developers from writting the UI in Visual Basic, the data engine in FoxPro, and the number crunching portions in VC++ or Delphi.

I don't think VFP is going to die. It is the quickest database engine for developing apps as easily as you can with VFP. Ok, I'm stepping down off my soap box now. I have to scroll WAY down there past all the "Forward to" names to find the [SEND] button. :)