>>Of course, they say it will ship next year. That means the end of next year. There's plenty of water that will pass under the bridge between then and now. I'm predicting early problems with VB7 since it's going to be a major overhaul.
>
>Take the easy predictions, why dontcha? < g > Any delay to VB7 will be good for VFP, but won't necessarily affect the final outcome. If it really is released at the end of 2001, that will be over 3 full years since the last release of VS... far too long, IMO. Market forces may dictate an earlier release.
>
>All those DevCon attendees are going to be annoyed that there will be no new VS rollout for them to play with. "Miami Hotel Bookings take nosedive..."
>
>Maybe the VFP team could put any delay to good use by incorporating VFP8 features into VFP7.

I spoke with Robert Green and Ricardo Wenger yesterday. I specifically asked since VS7 was now delayed, would VFP be getting Free Threading, etc. Robert essentially responded with "no comment" but did say that the VFP team would be spending the time adding additional features and completing the in-progress new ones.

>
>How about this for a scary thought... "News Flash - VB7 Team Falls Behind on implementing OO Extensions". Where might MS find a small team of talented developers who are expert in implementing robust, OO features, to get them out of their bind?
>
>"News Flash - VFP Dev Team seconded to VB Team for VB7 Rollout..."