>There was a developer where I work just today
>who sat in a meeting concerning development tools and made the statement
>to all that Visual FoxPro was going to go away in a year or two anyway.
>That past-Clipperhead wanted everyone to go to VB.
>
>Sheesh!!!!

MS have already committed to VFP 6/Visual Studio '98.

They would have to provide a good migration path to another tool before dropping VFP, considering those that make a living from FP (particularly those whose whole business is FP) will give them a lot of grief and would probably not use MS tools out of spite.


Remember the new Remote Data Objects with their client side caching is very similar in function to Offline Views and was actually written by the VFP team.
If MS is using the VFP development team to do strategic work instead of developing VFP 6 then does that indicate a shift in strategy?