>I don't apologize a bit for what MS did. Would I like to have new versions of VFP? Absolutely. Would I like to have had more marketing? Absolutely. Would I like to have seen MS create a VFP.Net? Absolutely.

Glad to hear it. If only . . .

>But...I don't blame MS for what they eventually (keyword "eventually") had to do. From a business perspective, it was a smart move. I don't blame MS for screwing up my business or career. It's not my responsiblity to manage and maintain those as I need them to be and based on what's happening in my customers' businesses and the tech marketplace.

My business and career are not screwed up, but they do have the power to force people to buy and learn new tools and pay for massive rewrites at their discretion. That's way too much power. Good for them, bad for the customers. VFP was working great and could have been continually improved as all software can be and as .NET is over time. Frankly, I'd love to see a law that language developers can't kill a language unless they can't find a buyer for it. They don't have to continue development, but they do have to try to let another company do it.