>
it remains a clear slap in the face to Visual FoxPro.
>

This is in your second paragraph. For the record, VFP is not a person and it does not have a face. It is not capable of feelings. This is why comments and complaints like yours are not taken seriously - because it starts with an irrational and illogical premise. VFP is a thing - a software development tool - nothing more and nothing less.

In reality, you don't take this as a slap in the face to Fox. Rather, you take it as a slap in the face to you. You - a VFP developer - are personally offended, insulted, etc.

I have always found this sort of co-dependant relationship - between some Fox developers and the tool itself to be facinating - and a little troubling. It is amazing to see just how much self-worth/self-esteem and person-hood is tied up in the product amongst many Fox Developers. To you - and several others - to debate the technical aspects of the tool is tantamount to calling your skills as a software developer into question.

You really need to learn the phrase "I am not my development tool...."

As for your comments - I see them as nothing more than a rant of an extremely PO'd person. That is your right - and I respect that. But - lets call a spade a spade. First - you do realize that you are placing this one case study under the microscope and applying more scrutiny than would otherwise be applied. Why? Because VFP was mentioned - and it was/is the outgoing technology. What if the piece were reversed? What if VFP was the incoming technology and .NET/SQL Server was the outgoing technology? You would be OK with that...right?????

Until the day comes when you and those like you can articulate a position that is not so wrapped up on emotion and irrationality - I question just how seriously you will be taken by MS, and those outside a rabid sub-seqment of the Fox Community.