>>>That’s just cyclic cryptic bull. It just refers you right back to the roadmap. If you are unable to answer the question (I can’t say the boss wont let me) or (Or I don’t know we haven’t decided yet) then just say so.
>
>>What do you think the benefit is of us saying what we don't plan to do (in an official way)?
>
>Well you wouldn't have a bunch of VFP developers running around all ticked off trying to decifer cryptic infomation....and you'd give a bunch of developers and businesses the ability to plan for the future.

Sorry but I don't see it as cryptic. There will not be a completely new version of VFP. There will be add on releases to VFP9 focused on keeping VFP playing well in the computer world, especially in relation to an evolving Windows and other Microsoft products (Office, SQL Server, .NET). That is good enough for me. One thing that is very important (wish number 1) is that my VFP applications don't *look* obsolete (I believe looking "modern" will come via VFP interaction with Indigo or Avalon or whatever the new look is called).

Looking at the business side, it is much easier and less costly to sell compelling add ons on a periodic basis that to create a full new version. VFP is a pretty mature product already and it's difficult to come up with wonderful new things. The main thing it's lacking is natively creating internet apps and MS seems set in not doing that because they say use ASP.NET. Maybe some of the add ons will be wrappers around ASP.NET that will ease the learning curve? (Wish number 2).