Re: Year 2000 Impact on Informix

KENDRICKS.CHERYL@heb.com wrote: > > DUH..... is for the dumb things people do! (LIKE YOU SENDING IN THAT > RESPONSE). If you are going to address comments about PRIOR postings that I > put out, please address them directly to me. If you plan to use parts of my > posting, then try including the gist of it. This is so others who did not see > the original thread at least know what you are addressing. > OK Cheryl. Here is part of your posting so people may get the gist of it. The original person who started this thread was only asking for some feedback on the year 2000 issue. I am sure he was not expecting to be ridiculed, belittled or even shot as you suggested in your comments as listed below. Don't waste peoples time with condescending answers that are not directly addresesd to the question. Kill this thread now or take it somewhere else. > Date: Thursday, 24 April 1997 17:52 CT > To: sblack@elsouth.com, > levinson@mds.lmco.com > Cc: informix-list@rmy.emory.edu > From: KENDRICKS.CHERYL@SAT > Subject: RE: Year 2000 Impact on Informix > > The problem is not Informix 5.X or 7.X. The problem is how did you design that > database? > > Did you define actual date fields as character verse using the data types > of date or datetime (duh!!!!). Go back and change them to either date > or datetime data types. > > How is your code populating this database? In Informix 5.X and 7.1 if you > enter two digits for a year and the column is data type date, well "Informix > products assume that the year is in the twentieth century and assign the > numbers 1 and 9 (19) as the first two digits of the year". > > Did some smart programmer or administrator change the environment variable > DBTIME or DBDATE to NOT use the century portion of date (duh!!! shoot them > you Y2K programmers). Change it NOW. > > In essences you will find the most major RDMS are Y2K complaint. The > problem is that the designer/programmer did not design/develop for Y2K or > better yet, let's just say century! So in mid 1998 I'm going to become a > part-time programmer (DBA now, was an Sr. System Analyst/Programmer) and > make good money fixing those programs!!!