Wrong date provided by @Now Dennis Rudin 31.Mar.05 07:11 AM a Web browser Notes Client 6.5.1Windows XP
Kenneth and the rest of the community,
A long time has passed since this post was submitted and this is actually not a solution to Kenneth's issue, but rather a simular problem which I haven't found any logical reason for yet.
We have an application in which about 200 new documents are created each month. There is of course, as in most workflow applications a field (DateTime) saying the created date and time of each document. This field is set to contain @Now.
In a number of documents lately (9 of them actually) the date provided by @Now for this field has been eighter one month ahead of, or one month previous to the actual current date, causing us some serious trouble.
I have checked the local settings on the effected users' machines and everything seems to be in order, and they at least claim not to have changed anything regarding the date settings themselves.
One strange thing that I have noticed though is that when moving this date into a multiple value DateTime field along with a number of other dates and then looking at the field from another time zone, all dates are adjusted to the current time zone (field set to use user settings) except for the date provided by the field mensioned above, where the date and time stays the same no matter the time zone.
According to the property box I can see no difference between this problem date and the "correct" ones, but it looks the same, exept from the date difference of course.
According to the debugger the problem date looks the same as the others, and is specified as variant, as are the others.