DB Century
Posted in 2000
Topics: General Discussion
I am currently using a very old version of Informix 4.10.UC2 ... I know it's very old , but it still works for us / except for a report date problem I have been having since Feb, 29th . I t doesn't recognize a leap year. All of my report dates are one day ahead . How can I fix this problem? I heard about a DBcentury command but I don't have any additional info on it! smosley
Shirlene Mosley wrote: > I am currently using a very old version of Informix 4.10.UC2 ... > I know it's very old , but it still works for us / except for a report date > problem > I have been having since Feb, 29th . I t doesn't recognize a leap year. > All of my report dates are one day ahead . How can I fix this problem? > I heard about a DBcentury command but I don't have any additional info on > it! DBCENTURY is supported by OL5.10+, IDS7.24UC8+, IDS7.30UC2+, IDS7.31, IDS 9.2x. It is a newly added environment variable to control the interpretation of 2 digit dates on input to better handle Y2K problems. It will not fix the 2/29/2000 bug which existed in all Informix products released before December 1999 or so. Your engine does not realise that 2000 is a leap year and so all dates after 2/28/2000 are off by 1 day. There is nothing you can do except update all rows with a date after that and reduce the day by 1 or upgrade to a newer version. There ARE many advantages to the newer Informix versions not the least of which is ongoing support including bug fixes. OL4.10 was desupported over 7 years ago. Art S. Kagel
DBCENTURY is an environment variable setting but your 4.10 database will not recognize it. I am not familiar with this specific problem on 4.10 but I am not surprised and recommend you upgrade to at least version 5.10... Hal Maner M Systems International, Inc. www.msystemsintl.com Shirlene Mosley <smosley@mcbusa.com> wrote in message news:8h8pu4$35f$1@slb7.atl.mindspring.net... > I am currently using a very old version of Informix 4.10.UC2 ... > I know it's very old , but it still works for us / except for a report date > problem > I have been having since Feb, 29th . I t doesn't recognize a leap year. > All of my report dates are one day ahead . How can I fix this problem? > I heard about a DBcentury command but I don't have any additional info on > it! > > smosley > >