Hi,when I create a document on the server (no matter with what client) I get this:
Created: 02/26/2007
Modified: 09/19/2007
Added: 02/26/2007
Modified: 09/19/2007
The doc is only created and saved, no agents are running, nothing else happens.
Why are my dates so shuffled?
Thanks
Marco
Subject: Date misbehavoiur
I think it’s because some dates are taken from the Server, and some from the Client, and one of them thinks it’s September.
If I was a betting man, I’d say it was the client, and that the user has been using the Microsoft date/time dialog as a handy calendar (see here )
Subject: RE: Date misbehavoiur
to see what time the Notes client thinks it is go to File > Mobile > Edit Current date/time
Subject: RE: Date misbehavoiur
to see what time the Notes client thinks it is go to File > Mobile > Edit Current date/time
Subject: RE: Date misbehavoiur
Sirs,it’s not the client, somehow is the database…here’s why: if I make a local replica of the db, delete the original on the server, replicate back the db on the server and create a doc, it’s no longer wrong. Note that this strange time offset occurs also on the log database documents, where no client process is involved. Furthermore, the dates around 09/19/2007 are evidently misinterpreted, as they only span from 2:57 to 3:05 even if hours have elapsed. That is, the offset to the predent date is not steady.
Any other clue?
Thanks
Subject: RE: Date misbehavoiur
I ran into a similar situation a few years ago when somehow our server’s time got shuffled about (it was jumping a few years ahead). Well, if the database or its documents is modified while the date is wrong, the system won’t update the modifed correctly. I think its something like, has this been modified since then? No because the date has yet to come to pass, so I’ll keep the date that’s in there.
Its been a long time now, but I think we had to recreate the database to correct it. Possibly a Compact (copy style) will fix it, but that’s a toughy.
Good luck and be sure to post your resolution if you find one!
Subject: RE: Date misbehavoiur
Sirs,it’s not the client, somehow is the database…here’s why: if I make a local replica of the db, delete the original on the server, replicate back the db on the server and create a doc, it’s no longer wrong. Note that this strange time offset occurs also on the log database documents, where no client process is involved. Furthermore, the dates around 09/19/2007 are evidently misinterpreted, as they only span from 2:57 to 3:05 even if hours have elapsed. That is, the offset to the predent date is not steady.
Any other clue?
Thanks
Subject: Date misbehavoiur
I think it’s because some dates are taken from the Server, and some from the Client, and one of them thinks it’s September.
If I was a betting man, I’d say it was the client, and that the user has been using the Microsoft date/time dialog as a handy calendar (see here )