OK, Claudio ... I tried it and you are partially right.

It works just fine in the client code, *if* the client code is .NET. In other words, .NET seems to be doing some behind-the-scenes trickery. If I try to run the same WebService in VFP, I keep getting an "Unknown Name" error (meaning the name of the Web method). Try it, you'll see what I mean. Could be a Soap ToolKit issue and maybe with Soap 3.0 it's not an issue, I have no idea.

Now, this may or may not be ok for some. But, we want our WebServices to work for any and all clients. Even though, at this point, they are only being consumed by .NET clients, we don't want that to be a limiting factor.

So, I guess I'll give up on the idea of overloading our WebService methods.

But thanks for giving me a fun exercise to do this weekend! <g>

~~Bonnie


>Hi, Bonnie.
>
>Try this:
>
>

>[WebMethod(MessageName="GetApparatusList2")]
>public string GetApparatusList(string GUID, string Message, long StationKey)
>{
>...
>}
>

>
>Doing like this, on the client you will call GetApparatusList, and all the mapping for the messaging will be done internally... you don't need to worry about.
>
>Sorry, I'm on a rush now... let me know either if you succeeded with this, or if you had some trouble.
>
>HTH