Instead of Foxpro.Net or FoxPro for .Net should we have FoxPo .Net connected?Time for another survey.


>I just read on here that Microsoft is revising its .NET marketing / naming strategy. For example, they are renaming .NET Server to Windows 2003 Server, and have introduced the concept of '.NET connected'
>
>http://news.com.com/2100-1001-979878.html
>
>(see other links also on Jan 10th)
>
>What is everyone's opinion with respect to whether this might have a positive impact on the positioning of VFP?