>Stopping work on VFP was a different issue. It had everything to do with:
>
>- Corporate direction. COM-based dev tools are being replaced with .Net-based tools
>- Corporate direction. SQL Server everywhere.
>- Cost of VFP vs. revenue
>
>I've said for years that when the last one became reality, VFP would be dropped.

'Cost of VFP vs Revenues' ??
What exactly was the 'cost' here to overweight income ?
Unless you count Loss of sales (SQL SERVER) as a cost.

I have no problem with (false) profit/loss calculation as such, nor with
(wishfull) thinking on behalf of MS strategic analysts;
If you understood my point; massive numbers of small and medium businesses arround the world are literally TRAPPED in Windows environmment because of production app (VFP) they depend on.

That EULA ensures that trap for the time been. But how fair (and legal) is this to hundreds of thousands SME's arround the world who will have to pay huge price tumorow (after win7) for that quantum leap in technology / production app coverage. How long this 'deadlock' can be preserved?

Market usually correct itself;
I can already see some Xbase younger brother raising into VFP successor and running VFP apps smooth under some cool/stable Linux Distro <vbg>