Dataset / Pacific Timezone Question

[Amos Soma]

I have a Web Service on a Web Server on the East Coast
which returns a serialized DataSet from my SqlServer at
the same location.

When the DataSet is read by my client in a
different time zone, the datetime columns have
been "adjusted" to account for the time zone difference
between server and client.

For example, if the value in a datetime column on my
database is '1/1/02 12:00 AM', when I retrieve it on a
client machine on Pacific Time, the value is '1/1/02 12:00
AM' in the DataSet on my Web Server, but when the
client "deserializes" the XML back into a DataSet on my
client, the value becomes '12/31/01 9:00 PM'.

Is there a way to disable this behavior so I get the same
dataset at my client that I sent from my Web Service?

Thanks very much

[Scott Allen]

Hi Amos:

The only way to prevent this currently is to send the date/time as a
string.

--
Scott
http://www.OdeToCode.com

On Fri, 17 Sep 2004 13:59:42 -0400, "Amos Soma"
<amos_j_soma@y_a_hoo.com> wrote:

I have a Web Service on a Web Server on the East Coast
which returns a serialized DataSet from my SqlServer at
the same location.

When the DataSet is read by my client in a
different time zone, the datetime columns have
been "adjusted" to account for the time zone difference
between server and client.

For example, if the value in a datetime column on my
database is '1/1/02 12:00 AM', when I retrieve it on a
client machine on Pacific Time, the value is '1/1/02 12:00
AM' in the DataSet on my Web Server, but when the
client "deserializes" the XML back into a DataSet on my
client, the value becomes '12/31/01 9:00 PM'.

Is there a way to disable this behavior so I get the same
dataset at my client that I sent from my Web Service?

Thanks very much