Ken,
I guess I would like more support from the MS tech people here for the .VFP. web service development you describe below and other areas of .vfp. web development. To me, at least, it seems like they're never the ones answering the questions people have on these subjects. Also, any encouragement for authors to write on the subjects would, I think, be a step in the right direction. I think development in these areas is hampered because of a lack of effort in these areas. For example, many people using web services are not aware how to access a network .vfp. database or MSDE/SQl Server by creating a COM+ package. I don't believe this is mentioned in any of the docs or whitepapers and yet, you'd have to agree, it's pretty basic. I guess it would be helpful if there was a more organized effort to describe .vfp. web development in the docs other than having to find a white paper which may or may not address the issue. I'm just trying to be helpful here rather than just critical if you're genuinely interested in improving the situation.
What's your perspective on this? Are people interested in using .VFP. on the web this way or not??
>
>What do you mean we are not supporting it? Ther are demos of VFP working with XML Web services and COM/.NET interop in every keynote session we do for the past year and more. Consuming an XML web service in VFP is very easy, and there are lots of samples and documentation on that topic. For publishing an XML Web service from VFP, the best way is to have an ASP.NET XML Web service be the wrapper and simply call a VFP COM DLL. There are articles on using the XMLAdapter with ADO.NET online, using the VFP OLE DB provider to access VFP data from VS .NET, etc. As I said in reply to your other post about this...
>
>It would be useful for you to list what specifically you think is needed, not generalizations like this. There are several whitepapers on this on MSDN for VFP, there are samples to download at http://gotdotnet.com/team/vfp, there are many whitepapers on Rick Strahl's web site http://west-wind.com on this (which we would not need to reproduce on MSDN since these are good articles), etc. If you list out exactly what you think is needed, I could get input from others wanting similar materials to help figure out what should be the highest priority items.