Creating an ASP .NET app allows you to work directly with a web site. The web services I have created have consisted of simple interfaces to date; which is easily done in either VB .NET or C#. i.e., there was no demonstrable advantage to VFP since I was not using the local data engine. When I say natively, I mean that I don't have to go through the process of creating the app components and then go through another set of steps in exposing it through the SOAP Toolkit. Functionally, does it matter? Probably not. As a developer, does it matter? I think it does. Creating web services in .NET to me, is a more seamless process.

Does this help???

>>The fact is, .NET can create web services natively. Whether this translates into a demonstratively better thing, that remains to be seen. Again, it was my intent to qualify my comment. In the end, I did say that I don't think there is much that can be done in .NET that cannot be done in VFP. This is a techical issue however, one that does not rule the roost.
>
>PMFJI, but this is a topic that I would like to know more. What does ".NET can create web services natively" means. Basically, I would like to know how is it different than building a Web Service in VFP.