>>Hi:
>>
>>Does anyone know anything about MS's plan for marketing VFP 7.0?
>>
>>Thanx,
>>Charlie
>
>They have never, and never shall, aggressively market VFP. I just noticed that they pulled an old FoxPro feature, UDF's, and installed it in SQL Server 2000 stored procedures. That technique alone will eliminate many "cursors". This is just another example of FoxPro technology being extracted and installed in another product.
>Soon, there will be nothing left to pull out of VFP and it will die a quiet death - don't hate me, I still love the product but MS's past marketing of the product proves their intentions to bury it.

Carl;

I have made this statement before and aggravated some developers with these words. Visual FoxPro is IMO the "step child" of development tools from Microsoft. But what makes it interesting is that over the years FoxPro and Visual FoxPro have incorporated features from VC++ and VB, which the other two languages do not share. However, it seems these implementations are not "full featured" and leave you asking for more.

Yes, Rushmore came out of FoxPro and found it's way into "another Microsoft Product". And ADO is based upon the VFP engine. So I guess we could create a bit of a list of such facts.

Since Microsoft owns all these products I see nothing wrong with sharing it’s own technology within it’s various product lines. It can only help Microsoft and in so doing it helps me as a developer. I will never get everything I want but that is life.

Tom