For quite a few years now I have had documentation on the web for software developers involved with calendars, dates, times, and time zones. While the original motivation for this document was Y2K avoidance and correction the document goes a lot deeper into proper use of dates and times. After some lurking here it just struck me that some readers in this group might have some good ideas about ways programmers frequently go wrong with time zone processing or good ways of processing zones that are too little used. Any worthy ides not already covered by my document that would be useful to programmers are solicited. The Best of Dates, the Worst of Dates. http://www.exit109.com/~ghealton/y2k/yrexamples.html ---------------------------------------------------------------------- ghealton@exit109.com http://www.exit109.com/~ghealton/ ---------------------------------------------------------------------- Computers are like air conditioners: they don't work well when Windows are left open