Re: Current century not being picked up

---- you wrote: > > The programme (The front-end that inserts/updates data ) in the table needs > to be re-compiled with DBCENTURY properly set. The programs could be storing > them in 20th century date formats. The DBCENTURY variable is only used at run-time Dude! I thought this question had been answered by one of the gurus, but I'll have a go. Derrick was right when he said he needs 7.20 for DBCENTURY support. Up until that version (excepting 4.20) any 2-digit years are taken to be in 1900, NOT the current century. My tip for the day Dude; use 4-digit years. > <deeky@my-deja.com> wrote in message news:84t0nd$4sg$1@nnrp1.deja.com... > > Hi all, > > > > We are running IDS 7.24-UC5.8 of IDS and 6.04 UC2 of 4GL and SQL. > > We are also running AIX 4.3.3.1 which has passed the IBM "fixcheck" Y@K > > test fine. > > > > Our problem is when we enter a 2 digit date "00" it is converted to > > "1900". I know using 4 digit dates is the answer, but unfortunatly the > > third party application allows for the entry of 2-digit dates. > > > > From what I have readon DBCENTURY I will need to upgrade SQL and 4GL to > > 7.2X in order to use DBCENTURY functionality. However, I was lead to > > believe that the current versions of these products are supposed to use > > the current cenrtury for year expansion as a default. This does not > > explain why if my system date is correct and my O/S is Y2K, how come > > "00" converts to "1900"? > > > > Any thoughts on my situation? > > > > TIA > > > > Derrick > > > > > > Sent via Deja.com http://www.deja.com/ > > Before you buy. > > AB ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com