Most of the posts I have seen are dealing with how the DST changes effect 2007 dates already entered into databases. My bigger concern is how date/times are displayed when opening older records. For instance a document with a date field of 10/29/2006 11:00 AM when opened after the OS patches have been applied will now read 10/29/2006 12:00 PM. We have many instances where we are opening older records to review, and needing these times to match any printed documents that may exists. The solution of running an agent against all date/time fields that fall into the window of discrepancy between this years and last years DST law does not seem correct. By running an agent you are actually changing the time, and I don’t want to change the time. If I change the time, the display is now correct, but any date difference calculation would now probably be inaccurate. Also, there are far to many records/database to go through to make sure this is done accurately and correctly,
The OS patch issued by Microsoft KB928388, seems to add a dynamic DST law within the registry file. One for 2006 and another for 2007. From a Microsoft inquiry we received the following response “Dynamic DST registry entries are not read by the OS. The only thing that the OS looks at is the base time zone information. The Dynamic DST entry is there for 3rd party vendors that need to modify the behavior of items that occur in the past”. If that is the case, I don’t see why Domino does not add multiple DST laws into the ini file so that it can pick the one that should apply. Instead it picks up the current DST law, adds it to the ini file, then applies this law to any date it finds.
Sorry for the rambling but I feel this is a big issue. If I missed some posts that I should be looking at please let me know.