Re: Year 2000

>From: "Histasp M. Khambata/NM/SEEPZ" <histaspk@meghdoot.mastek.com> >Date: Wed, 16 Jul 1997 11:33:07 +0530 >X-Informix-List-Id: <list.15478> > >I have a query regarding the problems one expects in the Year - 2000, >on account of the DATE. > >Would a complete change be required to applications, where a DATE field is >used in which only a 2 character year is accepted, or is there a simpler >method. As has been stated before in this forum, and as no doubt will be stated many times again, the only safe way to deal with years is to display 4 digits for the year. Even though (current) Informix products safely deal with the Year 2000 [see below], and all Informix products either already handle the DBCENTURY environment variable or will do very shortly, unless you show all 4 digits of the year, you cannot tell what the system has done to your 2-digit year unless you show all 4 digits. The 'only' change you need to make to your application is to specify all form fields for dates so that 4-digit years can be displayed. However, it is possible to write logic which relies on 2-digit years being converted to a date in the 20th Century (the current behaviour), and any such must be reviewed. For further information, you are referred to the c.d.i archives where the subject has been discussed extensively. Try http://www.iiug.org or http://www.dejanews.com if you don't have anything closer to you. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> PS: I decline to respond to messages with anti-spam in the return path. Note 1: Informix 3.30, the really old (1985 or earlier) pre-SQL database system has no concept of a year outside the 20th Century. Anybody still using it will need to think very seriously about upgrading now. Yesterday is a bit late for this! Of course, such people are unlikely to be reading this news group; however, we can but try to get the news to them. Note 2: I've heard a report that the Informix SQL-based products prior to release 4.0 have problems with the year 2000. I've been unable to substantiate that report, but if you are still using them, it would be worth checking rather carefully. If anybody does have access to the old products (eg ISQL 2.00, 2.10 or 2.10.03) and can check whether the old products recognize 2000-02-29 as a valid date with DBDATE="y4md-", I would appreciate the feedback.