>I think David Stevenson's response post did a great job in answering any open questions on this thread so far.

I didn't realize that DavidS was now the "leader" of the VFP efforts at Microsoft.

So...

1) VFP9 is the END OF THE ROAD for VFP versions.

2) The VFP Team - what's left of it - will deliver some add-on 18 months from now and well past 2 years after VFP9 was released.

3) This add-on is dependent on deliveries of other developmental software at Microsoft which has already seen slippage in both deliver date and feature set.
- This means we're back "in the box", that is, tied to a far out delivery over which the VFP Team - what's left of it - has no control.

4) The VFP Team - what's left of it - will squeeze in a service pack some time around the end of this year.

5) The VFP team - what's left of it - is pre-occupied with enhancing .NET and we (VFP developers) can hope that that work will make adopting/exploiting .NET simpler.

The saving grace in all of this is that VFP is such a great product and its market still so wide that we (VFP developers) should still be able to deliver great products to our users despite all this help from the VFP Team.

That seems to sum it up for me.