>>>
>>>But none of those decisions affected the actual product.
>>
>>Craig, do you have the inside track on this? Else how do we know?
>
>I don't know any more than anyone else. However, the simple removal of VFP from VS.Net would not change VFP itself as it didn't use the VS IDE. >The addition of MSDE is a bonus, but its inclusion again doesn't change VFP itself.

In the public beta of VS.NET that I looked at which did include VFP, the VFP development environment offered the traditional Fox interface, and also the Common development environment. Admittedly, I did not spend a lot of time with it, and I was also trying to do an analysis of the changes in VB and the introduction of C#.

Personally, I like the stand alone environment, but have also expressed concerns about the marketing of the product. Not everyone is going to purchase Universal subscriptions to MSDN, even though for developers, that is the most economical way to go. Clients that purchase the stand alone Visual Studio .NET will no longer be exposed to VFP, unless they want to pony up an additional $500 for VFP. On the other hand there may well be an increase in demand for migration of Access applications to VFP or a more robust product. <g>