In microsoft.public.money, Art McClinton wrote:

- quote -

I expect daylight savings to be not in effect, so the expected time
and date would have been about <DTSERVER> 20080306004400*. -- 44
minutes after midnight the next day GMT. Your examples have a
reasonable <DTCLIENT> . Since the <DTSERVER> specify the timezone as
[-5:EDT], those times do not default to GMT. The timestamps look
consistent to me.

19:44 +5 gives 24:44, or 00:44 the next day.

- quote -

When I try to update my account with Fidelity Investment services tonight
(yes the netbenifits side as all other accounts are working) I get the error
message "Invalid Date Range". I turned on the registry setting to save the
transaction files and found:

From first RQ file
<DTCLIENT> 20080306004421.682</DTCLIENTFrom the first RS file

<DTSERVER> 20080305194424.555[-5:EDT]</DTSERVER
From the second RQ file

<DTCLIENT> 20080306004425.198</DTCLIENT
From the second RS file

<DTSERVER> 20080305194427.081[-5:EDT]</DTSERVER
I checked the machine time and found it was approximately 7:44 pm on March
5th with day light savings time enabled. I also have set the Eastern time
zone.

I am running Money Plus Delux. I have not seen this before.

Any ideas?

I can send the files as they are small if that would help.

Thanks

Art McClinton