efnkay
02-23-2011, 07:07 PM
** This thread discusses the Content article: Partner TechTip: Simplify Your Field Expansion Projects (http://www.mcpressonline.com/tips-&-techniques/system-administration/partner-techtip-simplify-your-field-expansion-projects.html) **
We didn't actually leave our grandchildren without "date" problems in some cases. We all pretty much create and use 8-digit dates (*ISO or *USA) nowadays, or timestamps, because DASD has by far blown-away most worries about using up too much disk with those un-neccessary century values.
Still there are seven digit dates in use out there, where the century digit is determined by some "windowing" effort over the two digit year. Like year < 40, century = 20, year >= 40, century = 19.
So if some of this code is still in use by then...We have successfully setup our grand-kids with the soon to be famous 2039 date problem...!!! Can't wait for that one to roll around. Hoo-hoo :-)
We didn't actually leave our grandchildren without "date" problems in some cases. We all pretty much create and use 8-digit dates (*ISO or *USA) nowadays, or timestamps, because DASD has by far blown-away most worries about using up too much disk with those un-neccessary century values.
Still there are seven digit dates in use out there, where the century digit is determined by some "windowing" effort over the two digit year. Like year < 40, century = 20, year >= 40, century = 19.
So if some of this code is still in use by then...We have successfully setup our grand-kids with the soon to be famous 2039 date problem...!!! Can't wait for that one to roll around. Hoo-hoo :-)