>- VFP was the first MS development tool that made it easy to create web services

Not true. Creating COM Components in VB was easy. And - the SOAP toolkit made it easy to create web services. Some time ago, I took VFP 6 components + the SOAP Toolkit in the end - was just as easy as the VFP Wizard. Further - the VFP wizard in fact cuts you off from the full functionality the native SOAP Tools offer.

>- VFP was the first MS product to be certified for Win95

And this meant what?

>- VFP was object oriented years ahead of VB

So what? While you may have perceived this as an advantage - the world at large could care less.

>- Rushmore technology was ported to other MS products such as Jet database and SQL Server

This is another over-exaggerated thing. What demonstrable benefit did this have?

>- Client side ADO record sets are based on the VFP cursor technology

Again, so what????


>As for VFP not being strategic, MS has many other products that you could argue the same point. How about Works, Mac Office, or even Access for that matter.

May be true - but Fox developers don't care about works, mac office, or access. While you seek to bolster your point through analogy - the tools you enumerate can easily be distinquished from Fox - diminishing the effacy of your analogy. If you are going to analogize - best to do so with comparable products. Limit your view to developer tools. For example, COM is not strategic to MS - and therfore, products like VB 6 are going into maintence mode.

>
If you want to see a group even more upset over being left behind by .NET, talk to the Access people.
>

I think the VB 6 people may be a bit more frustrated.


>
>>I’ve been using foxpro since the relese of 2.5 and heres my take on it. Foxpro has always been a step behind the rest of microsofts development tools. A great if somewhat simple example intellisense. VB had it from version 5 on foxpro didn’t get it for Years. And like some of the other feathers It doesn’t work properly! Go into a VB IDE and type
>>With text1
>> .text
>>end with
>> when you hit the period the intellisense works. Now try it in fox 7, 8 or when its released 9 it wont work (this malfunction also includes variables that are in scope but outside of the method they where declared in). another great example is window handles.Just try playing an avi for a splash screen on a form that’s desktop .t. and show as toplevel.
>>

Fox has been more than 1 step behind. As for intellisense, I turned it off because it does not work in a way that is close to being correct. Where in VB 6 and in .NET - it helps you - the VFP 7 implementation is a hack - functionality kludged up and layered on an existing code base - and as a result - is a liability more than an asset.


>>
>>A lot of fox programmers have jumped ship to .Net in part or in total. I wish Microsoft would fully support the product or kill it off!
>>

An interesting study would be to take a snap shot of the upper tier of Fox developers from 5 years ago and fast forward to today to see what they are doing.