>Hi RObert, I was there but look a bit older now. That photo on the screen here at UT was when I was a Navy Officer serving on Oepration Desert Shield/Desert Storm. I was called to Active Duty at Port Hueneme, California, in 1990-1991. I will have to soon and regrettably put up an older man's photo.

The phrase "older man's" is misleading, it's "experienced man". :-))

And by the way, my opinion is clear given the current status. As long as VFP can be used on all the available Windows versions which are in use by my customers, I see absolutely no reason to look for any alternative to VFP. VFP9 is mature, meaning that it has as good as all the commands, functions and features you need to create just about any kinds of business applications. And the few features it is missing, can be added by easily avalianle third party products. And if you need more data capasity or security, you can use choose between a variety of SQL back ends.

VFP has been available for nearly 20 years, meaning that I have about 20 years of experience with VFP and its predecessors. How long has .NET been available, and how much experience has the .NET gurus in comparison? Can you create an equally fast application in any language as quickly as you can in VFP? Absolutely no. Why change your favorite tool when there is absolutely no reason to change, other than some hype created by poeple who mostly have hidden motives? I prefer to be a leader, and not a follower. I make my decisions based upon my own needs, my customers needs and knowledge, not on hype and mostly false rumours.

If MSFT unplugs VFP soon, so what? I can still use it for the next 10-20 years or more, and by then the situation is so completely different anyway! I have no looking glass into the future, but I can see today quite clearly.