Well, Y2K this ain't.

The DST change is typically going to be handled by the parts of the
programs that process and/or "read" local time zones from various parts
of the computer systems. For PCs and servers, that is in the operating
system for the most part, which needs to be patched. Some software may
read the system time, but rather than see the local time, will read the
time as GMT / UTC and convert GMT to the selected local time zone for
that application. Clearly, if the software isn't patched, there will be
mismatches between time zones.

My guess is that somebody in your firm read this article
http://www.networkworld.com/news/2007/012507-daylight-saving.html last
week and saw the line about "ensuring record compliance, for example,
could be at risk."

My guess is that the big issues will be calendaring applications, plus
some issues with document management systems where authors are creating
documents with different time stamps.



Patrick Cunningham, CRM
[log in to unmask]

"Those who would give up essential liberty to purchase a little temporary safety deserve neither liberty nor safety."
Benjamin Franklin, Historical Review of Pennsylvania, 1759

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance