>Ok, here's an interesting one. Maybe someone else already went into that one. IAC, here's some explanations. I would also be interested in hearing some comments if others faced that situation as well.

Not me, but what you comment is quite interesting.

>However, the problem resides for users having a time zone set to something else than the time zone of the server. So, assuming it is 12h45 our server time and the user is having 2h45 local time with the same day, when the date value is received at the server end, it is converted to the date passed minus 1.
>
>When having discussed that with Microsoft, it appears that this is by design. This is the expected behavior.

Expected? wierd

>However, an interesting observation is that if the client uses a .Net Web Service or a VBA for example to call our method, it'll work. We only experienced the behavior from a client using VFP.

Then this is a wierd expected behavior.

>But, as Microsoft says, this is by design and this is one way to resolve that issue.

Wich one? using string instead of date?