>>
>>Or, MS could just be using VFP as a headlight to keep the VB coders frozen on MS Dev tools while they complete their C#-.NET plans.... then drop VFP like a hot potato.
>
>The perception among some of the non-Fox developer community is that the dropping has already happened. I do not agree with that, but I carry none of the weight that MS does when a relatively minor change in focus or position takes place. The ripple effect is alive and well, and needs steady guidance.

True. I see us using VFP6 if not 7 here for at least the next 10 years, which means we won't be going .NET nor XP, but probably stay at W2K Pro.