>
>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#.

The Fox support in the Common Development environment was only for code-based middle-tier components.

>
>Personally, I like the stand alone environment,

I have never liked the VS IDE. It's too cluttered. Not enough screen real estate to work efficiently.

>but have also expressed concerns about the marketing of the product.

MS has promised increased marketing, yet you are complaining before even seeing what it's going to be.

>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.

IMO, they won't pay full price, but some kind of upgrade pricing. However, if you look at purchasing VS, then adding VFP, you've almost paid for an MSDN Universal.

>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>

That would be very good.