Strange Remoting Behavior When In a Different TimeZone

[googlegroups]

We have an application that is run in many timezones and uses remoting
to access the DB. I have one screen that will only save if the user is
in the same timezone as the server. I can reproduce this on my
development machine by simply changing the timezone. When I use
remoting and a different timezone, the remoting call hits the webserver
(I verified through the web server logs), but never actually makes it
to the DB. I put some code on the server side to return an error for
any DB call with my username. It doesn't fire. It's the strangest
thing. We do have a couple of DateTime values in the dataset we are
saving, but we also have them in other places in the system and they
work fine elsewhere. Please help!

[Cor Ligthert]

Hi Kirk,

I think that you have to break up your problem to get help (in a new message
otherwise you only reach probably me and I assume that there are some parts
in it what is not my best part). It is too much described in my opinion
however gives very few information how you do it.

What even is not clear for me is, are you using webforms, windowforms or
webservices and where is than the remoting placed?

Cor

<go**********@kirklarsen.com>

We have an application that is run in many timezones and uses remoting
to access the DB. I have one screen that will only save if the user is
in the same timezone as the server. I can reproduce this on my
development machine by simply changing the timezone. When I use
remoting and a different timezone, the remoting call hits the webserver
(I verified through the web server logs), but never actually makes it
to the DB. I put some code on the server side to return an error for
any DB call with my username. It doesn't fire. It's the strangest
thing. We do have a couple of DateTime values in the dataset we are
saving, but we also have them in other places in the system and they
work fine elsewhere. Please help!