>It is also my reaction. I guess by design is an overall representation which could include some isolated issues like this.

Yes, that is expected in VFP, but I think you put that in .NET works. So different results. I don't expected that :)

>Claudio made some tests on that one and confirmed me that. Maybe he could provide more explanations on additional comment on this.

It would be great

>>Wich one? using string instead of date?
>
>I'm not sure what you mean here. My comment was only when defining a parameter as date. As for other reaction that could happen with a string type, I don't have any idea nor having found anything else in regards to that with string. In my case, I updated our robot to check for a new version of the WSDL file. Once discovered, he'll replace in the WSDL file all occurences where xsd:datetime should be replaced with xsd:date.

Well I say to use DTOC, like:

loUniversalThread.GetMessage(DTOC(DATE()))

and

FUNCTION GetMessage(tdDate as string) as String
...
ENDFUNC

So you say that with date type in the WSDL this works?