>>>>Hi Mike,
>>>>
>>>>We (VFP developers) all know that MS wants to kill the fox. I'm surprised by your reaction because I was sure that by now you'd be exclusively working with .net. By that I mean for your new projects.
>>>
>>>If Microsoft wanted to Kill Foxpro, they would STOP putting out new releases. Heck, that's what they did to VB, why would they hesitate to do it to VFP?
>>
>>Yes but they did'nt forget to leave a door open with VB.Net
>
>True, but VFP coders can walk through that door too. The combination of:
>
>1. VFP .Net tool kit
>2. VB.Net
>3. VFP OLE-DB provider
>
>You actually have a pretty damn good version of [what] VFP.Net [would be].
>
>Heck, if all they did was write a .Net managed provider for VFP databases they could drop VFP and there's not much you couldn't do. (Not that there is really anything you can do with VFP that you can't do with .Net now.)
>
>Of course, you would loose all the backward compatibility.
>
>BOb

Backward compatibility is like specifications! Who needs them? They are both for wimps! :)