Re: Year 2000 Default Behavior

In SQL (ODS 7.22) there is something called DBCENTURY that can be set to influence how Informix handles 2 digit years. The default setting/behavior is 'C' which means that Informix will expand the date to the whatever is closest to the current year. For example if you enter '50' you get 1950, if you enter '25' you get 2025 and so on. There are other available values for DBCENTURY that you can find in your SQL reference book. The default seems like a logical default. I am not a 4GL person, but I would suggest setting up a test and seeing what you get.- Good Luck -- Bob Carts - SAIC rcarts@agccs.lmco.com 703-813-2914 Jeffrey J. Dreps <infopro@rust.net> wrote in article <33B276E6.282A@rust.net>... > Can anyone point me to information regarding how Informix 4GL and SQL > handle the entry of two-digit years? Certainly the database is Y2K > compliant in the way that is stores date fields, but one of our > customers has asked us to respond to a 40-page Y2K questionaire. I am > wondering how Informix will handle the entry of two-digit dates: i.e. > will it choose the closest date? Can we specify an upper limit for > years which should be +2000 rather than +1900? > > The only info I could find was in a 4GL reference that stated that "19" > would be assumed for all two-digit years. This would require that all > entry screens be modified to accomodate 4-digit years or post-processing > of all fields in the program logic. Can't Informix be made to do > something reasonable automatically through compile or run-time > parameters or environment variables? > > Any help would be greatly appreciated. >