You might be right, but, if developers knew MS was behind protecting their investment in Visual FoxPro code when they want to take it to the web, they would be much more likely to upgrade, I think. I wouldn't want to have to rewrite all or most of my vfp code in C# or VB.NET just to get it on the web. Just good examples of VFP interop with .NET would help. Also, including developments like COM debugging affect all VFP developers and, if this was integrated into the new version,it would possibly increase upgrades, in my opinion...

>I'm not sure how much "cutting edge" things will help them sell the product. ASP.NET sets the bar pretty high as far as web-development goes. Why try to compete with another product that already "does" web development? If I'm going to be using VFP data, or exposing an existing VFP app. to the web, there are already good third party tools to do this; having this built-in or some extra things to make it a bit easier would just be icing on the cake. It wouldn't be the main reason I'd upgrade, though. If I'm going to be doing a new site, or one that uses SQL Server, I'll choose ASP.NET almost every time.
>
>MS gets pounded with each release about them not upgrading basic things (and REALLY important to almost any app) like the report writer. I think this is why they spent a good chunk of development time on it. I don't think a lot of developers are looking for "cutting edge" features. I know they want the features they add to be the things asked for by a majority of developers. I really think that a lot of developers requested the report writer to be updated. I'll be honest, I wasn't too excited about it to begin with, since I'll use Crystal whenever I need more functionality. However, after playing with the beta, there are some cool things that I'll be really happy to be able to add to my existing VFP reports because of the enhancements.