I just think it's an extra benefit you get if you're writing your WebService in .NET, but it's not standard WebService stuff, so it shouldn't be used.

Much like having a WebService return a DataSet. That'll work with a .NET client easily enough, but not with other clients unless you use the XMLDOM to parse the object that's returned, since it *is* an object that's returned, not an XML string. So, bottom line with that is never return a DataSet, return DataSet.GetXML() instead.

Same goes for this overloading stuff ... it's probably not standard behavior, so don't do it.

~~Bonnie



>Hmm, do you want to know something interesting?
>
>I just tried to access the overloaded method through VBA on a Excel macro. Well, the call for the first method´s signature defined works fine; but the call to the second one, not (it gives me a SOAP mapping error, saying that´s a type mismatch).
>
>So, I still didn´t figure out whether that´s a problem on the SOAP Toolkit, on in .NET.