It would be great if VFP9 just had some good web examples: web services, web apps, interop with ASP.NET. I'm hoping the final product will improve on what I've seen so far. And the web aspect touches on many other useful features. One of them, which John Koziol said he would investigate, is COM debugging within VFP. It's already been done, just as my product has. However, to include it, to document it, and have good examples is a big step up from where it's at now. If developers knew MS was behind protecting their investment in vfp code when they want to take it to the web, they would be much more likely to upgrade, IMO...

>Claude,
>
>>I don't want to belittle the effort on the new Report Writer, but, it seems the focus of the new enhancements and feaures are less than inspiring (since about VFP7). In case MS has not been listening (and I know they have) the world is moving to the web.
>
>The MS strategy for web development is very clearly ASP.NET. I don't think it has to do with them not listening -- they have clearly made their decisions about the recommended way to develop web applications. There are enough third-party products or resources out there (including yours) to give the VFP community lots of options in addition to (and in combination with) ASP.NET.
>
>In the case of the Report Writer, there ARE significant enhancements to it for creating HTML output from existing or new reports -- that certainly shows attention to web concerns and is just the tip of the iceberg in what can be done with the ReportListener approach to object-assisted reporting.
>
>I do understand, however, your concerns from your particular perspective (which can sometimes come across as very narrowly focused) about adding more web capabilities to the base VFP product. Based on what I have observed and heard, I think feature decisions usually come after an analysis of existing alternatives or work-arounds ("Is there already another way for VFP developers to accomplish this need right now?") along with weighing the company's overall strategic direction and balancing out available development resources against a LONG laundry list of possible enhancements.
>
>I, for one, am very glad that they put the effort into creating such an extensible Reporting System, although it may take a long time for VFP developers to realize