>-snip-
>>>
>>>I guess I'm dragging the point too far out, so let me just summarize that this VFP programmer will not let VFP die if it went .Net.
>>
>>You gonna go out and buy enough copies?:-)
>>
>
>Just enough :)
>
>(that would be mine)

LOL!

>If the benefits outweigh the drawbacks, why not. As you can see this issue is kind of like voting, for some developers it would no longer be VFP and for others a leaner and meaner one.
>
>>Seriously, I believe that we've heard from the Foxteam itself that the native data munging capabilites would be lost if VFP became a CLR compliant language. However, even if this isn't the case, there's one "feature" that we'd certainly lose.
>>
>>Shortly after the release of the 8.0 beta, one of the members of the Foxteam (it may have been Ken, himself) noted that the product was being driven by the users' needs and desires. This was underscored by the large number of items that were requested in the wish list that made the product. This is what we'd lose. I, for one, am not so willing to give it up. Why would we lose it? Simply because we'd have a smaller voice in the overall direction of the product, and that product isn't VFP or VB or even C#. The product is the CLR. That determines what we can have and what we can't.
>>
>
>I agree with you here, letting the community decide is a healthy compromise. I guess I better put my CLR-compliant Cursor Adapter in there sooner rather than later :)

< g >

>Now that I think about it, ADO.Net can be manipulated to "feel" like run-of-the-mill VFP data so I can put another entry for the ability to manipulate ADO.Net datasets.
>
>Now this is getting interesting.. ;)

There you go!< s > I've enjoyed the exchange Crescencio.

Best,