Hi

 

Dates have always been interesting and at times challenging to get working - especially for all of us not living in the US (!). Just this morning I found an error in the LotusScript Format method that will use the American algorithm to calculate week numbers (no matter what the Notes client has been set to use...). In Europe we have use the ISO standard to return the correct week number. Yes, week numbers actually differ between the US and Europe (for this and last year). Sigh!

 

But back to your question. It all comes back to the format of the date. I do not know what conversions you have made. From the dates you have specified it is impossible to say whether the format is: dd.mm.yy, mm.dd.yy, or yy.mm.dd. In the last format your logic is actually true... ;-) The next thing that could trick you (but not with the examples you have given) is that the (built-in) code may try to "help" you. This was true for the first versions of the webservice classes in version 7 where the date 2010-10-31 was correctly interpreted as a date in October, whereas the date 2010-11-04 incorrectly was interpreted as a date in April (both using the date format yyyy-mm-dd which is the "normal" for XML dates) - sigh, again...!

 

I suggest you try to ensure that your date formats are enforced. One way of doing this (say if you are converting between strings and date objects) is to create a date with a format that you know, say 1999-12-31 and then you can substitute your date values into the string using a simple string replacement and really ignore the format that the current computer was using. On a server you may be able to control it - but if your application is run on more than one computer you may inevitably end up with these kind of challenges...

 

/John