Especially, since I haven't seen a rule yet that if a vendor comes out with a bad version of a product, you need to switch tools. If .Net is not successful, folks will just stay in the VB6 camp.

The arguement that people would switch to VFP if VB.Net doesn't make any sense to me. From what I understand from reading postings by folks like Rick Strahl, you would gain absolutely nothing by switching to VFP from VB after .Net. The purpose of MS coming out with .NET is to address the shortcomings in developing under IIS today. Switching to VFP would not gain you anything whatsoever. And you would still be stuck with the same shortcomings.

PF

>>
>I think with the trouble that VB is going to go through with the next upgrade could be a prime opening for the red furred fox to make its move.
>>
>
>It troubles me that folks feel that this sort of initiative has merit. Let's say for example that you were going to underwrite a proper marketing campaign for VFP. You are probably talking about a campaign that would cost well over $1,000,000. Do you think you could fund such an initiative. Dream all you want. But at some point, you need to wake up and smell the Joe....
>
>< JVP >