Y2K.01 bug
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Thats what you call a short term view. Probably a contractor either building in some job security or they were building a tactical system that was designed to last 1-2 years, not thats not even a valid excuse for this stuff.
Never underestimate the power of human stupidity RAH
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Funny about that. For my sins, I'm stuck with maintaining an ancient (as in 16-bit DOS exe's) system where the original developers decided that 31 Dec 2010 was past the end of time. Not only that, the value is in a .h, so it's compiled into instructions all over the place:
cmp dx,2010
jg bad_dateOne of two of them aren't too bad, but when some sites have been compiled with different compiler versions/optimisation settings it becomes a right royal PITA. And, of course, every site out there is different, and we can't rebuild from source... :mad:
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Thankfully, no. Am I the the lucky one? :-\
Anna :rose: Having a bad bug day? Tech Blog | Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Funny about that. For my sins, I'm stuck with maintaining an ancient (as in 16-bit DOS exe's) system where the original developers decided that 31 Dec 2010 was past the end of time. Not only that, the value is in a .h, so it's compiled into instructions all over the place:
cmp dx,2010
jg bad_dateOne of two of them aren't too bad, but when some sites have been compiled with different compiler versions/optimisation settings it becomes a right royal PITA. And, of course, every site out there is different, and we can't rebuild from source... :mad:
-
... does that mean you're patching the apps with a disassembler?
The European Way of War: Blow your own continent up. The American Way of War: Go over and help them.
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
I built in a hard limit to a VB6 app I originally wrote in 1999, which wouldn't work past 31 December 2007. Then I had to issue a fast upgrade on 1 January 2008. Yes, I didn't think I'd still be supporting it eight years later. Edit: I can't tell decades apart, apparently.
-
I built in a hard limit to a VB6 app I originally wrote in 1999, which wouldn't work past 31 December 2007. Then I had to issue a fast upgrade on 1 January 2008. Yes, I didn't think I'd still be supporting it eight years later. Edit: I can't tell decades apart, apparently.
None of us writing that old legacy code ever believed in 25 years in the future. But damn that future came up and bit us in the behind faster then we thought possible. I mean who at 25 thinks they are writing code to last more then 10 years, and at 2000 I would have been 49 - who lives that long?
-
Interesting message[^] in the general discussions forum._decade = substring( my_YYDDD_DateString, 1,1 ) ;--return a YYYYDDD date string.
if( decade = 0 ) then
return "20" || my_YYDDD_DateString ;
else
return "19" || my_YYDDD_DateString ;HOLY MOLEY! They took a Y2K issue and fixed it by creating a Y2.01K issue. Given that the Fiscal Year where this code is used ends on Sep 30, they've got about 56 days to get it fixed!_ Anyone seen this kind of thing lying around?
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP