But you still, are, in fact, calling procedures and receiving back function
return values.  The transport mechanism may be a complete XML document, but
what you are doing (why you are using the services) doesn't change
fundamentally.

That's probably way too much code, but here is someone that had the
same problem:

http://groups.google.com/group/microsoft.public.dotnet.framework.webservices/bro
wse_frm/thread/9d0a4c200117dc1b/3cc244dfa9208c7f

That is where I got part of my information from.

Here is the code up to that point in my .asmx:

using System;
using System.Web;
using System.Web.Services;
using System.Web.Services.Protocols;
using System.Runtime.InteropServices;
using System.Data.Odbc;
using System.Configuration;
using System.Diagnostics;
using System.Data;
using System.Xml;

[WebService(Namespace = "http://tempuri.org/")]
[WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)]
public class Service : System.Web.Services.WebService
{
   public Service () {

       //Uncomment the following line if using designed components
       //InitializeComponent();
   }

   [WebMethod]
   public string HelloWorld() {
       return "Hi";
   }
   [WebMethod]
   public XmlDocument GetDataFromDB(string name)
   {
       string errorMessage = "";
       XmlDocument myDatas = new XmlDocument();
...

In my client .aspx:

   protected void Button1_Click(object sender, EventArgs e)
   {

     DataBindFrmWS(TextBox1.Text);

   }

Thanks again for any help.  Everything works, as long as I don't pass
it a variable.

This