>>Then this is a wierd expected behavior.
>Claudio made some tests on that one and confirmed me that. Maybe he could provide more explanations on additional comment on this.

Let me jump in here... :)

there was a lack on my tests, but that confirms the behavior expected explained by Microsoft.

On my tests in VFP, I was passing Date() as a parameter...
In VS.NET, I was passing System.Date.Now...
In VBA, I was passing Now...

If I had passed DateTime() in VFP (as I did later...), the method returns the expected results... that´s because with the time (hour) informed, it mustn´t try to realize anything about timezone. So, if the WSDL expects a DateTime, and I just pass a date, it´ll try to figure out the time...

Anyway, there IS the problem that VFP COM TypeLib maps Date to DateTime, which affects the way the WSDL file is generated.