1. Windows Y2K adjustment
- Posted by Mike Sabal <MikeS at NOTATIONS.COM> Sep 15, 1999
- 451 views
Just a little warning I picked up yesterday. This affects some date calls = in some Windows programs, including Lotus and Excel. In the Control Panel = -> Regional Settings, select the "Date" tab. There are two sections here, = Short Date sample and Long Date Sample. The Short Date sample defaults to = "00" style years, but has the option to change to 4-digit years. On = Windows 98, it also allows you to choose the cutoff for 2-digit years. = Hope this helps avoid a few headaches. Michael J. Sabal
2. Re: Windows Y2K adjustment
- Posted by David Cuny <dcuny at LANSET.COM> Sep 15, 1999
- 456 views
Mike Sabal wrote: > Just a little warning I picked up yesterday. I've seen the warning - it's bogus. It doesn't matter what you display the date as, internally it's still a 4 digit year. -- David Cuny
3. Re: Windows Y2K adjustment
- Posted by Mike Sabal <MikeS at NOTATIONS.COM> Sep 15, 1999
- 438 views
I thought as much as well, but I made the adjustment to make a few people = around here happy, and there were some spreadsheet programs affected. I'm = just thinking that there must be a Windows API call that actually uses = that value; and some programmers may errantly use it in some calculations. = =20 >>> David Cuny <dcuny at LANSET.COM> 09/15/99 11:46AM >>> Mike Sabal wrote: > Just a little warning I picked up yesterday. I've seen the warning - it's bogus. It doesn't matter what you display the date as, internally it's still a 4 digit year. -- David Cuny
4. Re: Windows Y2K adjustment
- Posted by "Cuny, David" <David.Cuny at DSS.CA.GOV> Sep 15, 1999
- 382 views
Mike Sabal wrote: > I'm just thinking that there must be a Windows API > call that actually uses that value; and some programmers > may errantly use it in some calculations. I did a web search when I got the 2/4 digit warning from a friend, and apparently it's in such wide circulation that Microsoft issued a reaction to it. They claimed that it makes no difference, if it makes you feel any better. -- David Cuny
5. Re: Windows Y2K adjustment
- Posted by Joe Otto <jotto at NETZERO.NET> Sep 15, 1999
- 391 views
- Last edited Sep 16, 1999
Well, the real scoop is that it shouldn't make any difference - but it might anyway. The date/time is actually stored internally in a 64 bit integer reflecting the number of 100 nanosecond intervals elapsed since 1-1-1601 or some oddball number like that. In other words, the internal format is sound. This same 64 bit integer is what Windows returns to the various applications, run-time libraries, etc. that request the date. So the date is ok up to that point. Here's where some problems come in... Programs (such as Excel or Access) use the regional settings to format dates to output whether it's to screen or to a data file. If data is exported with 2 digit years to a file, then that file imported into another application, it's up to the second application how to interpret all those 2 digit years. And there's absolutely NO guarantee that it'll get them all right. In short, it shouldn't affect the normal user at all. But if you do any application to application exports / imports, I'd check closer before dismissing it. Joe PS ALWAYS watch out for (and double check) the Microsoft PR machine. -----Original Message----- From: Cuny, David [SMTP:David.Cuny at DSS.CA.GOV] Sent: Wednesday, September 15, 1999 11:45 AM To: EUPHORIA at LISTSERV.MUOHIO.EDU Subject: Re: Windows Y2K adjustment Mike Sabal wrote: > I'm just thinking that there must be a Windows API > call that actually uses that value; and some programmers > may errantly use it in some calculations. I did a web search when I got the 2/4 digit warning from a friend, and apparently it's in such wide circulation that Microsoft issued a reaction to it. They claimed that it makes no difference, if it makes you feel any better. -- David Cuny ________________________________________________________ NetZero - We believe in a FREE Internet. Shouldn't you? Get your FREE Internet Access and Email at http://www.netzero.net/download/index.html
6. Re: Windows Y2K adjustment
- Posted by Michael Nelson <mike-nelson-ODAAT at WORLDNET.ATT.NET> Sep 16, 1999
- 372 views
I work professionally with MS Access databases and Joe Otto's information on regional settings is 100% correct--an Access database I designed to be Y2K compliant couldn't handle dates in the year 2000--until I changed the Windows setting. This probably has no effect on Euphoria, but most of us use MS applications, too. --Mike Nelson -----Original Message----- From: Joe Otto <jotto at NETZERO.NET> To: EUPHORIA at LISTSERV.MUOHIO.EDU <EUPHORIA at LISTSERV.MUOHIO.EDU> Date: Wednesday, September 15, 1999 8:30 PM Subject: Re: Windows Y2K adjustment >Well, the real scoop is that it shouldn't make any difference - but it >might anyway. > >The date/time is actually stored internally in a 64 bit integer reflecting >the number of 100 nanosecond intervals elapsed since 1-1-1601 or some >oddball number like that. In other words, the internal format is sound. > >This same 64 bit integer is what Windows returns to the various >applications, run-time libraries, etc. that request the date. So the date >is ok up to that point. > >Here's where some problems come in... Programs (such as Excel or Access) >use the regional settings to format dates to output whether it's to screen >or to a data file. If data is exported with 2 digit years to a file, then >that file imported into another application, it's up to the second >application how to interpret all those 2 digit years. And there's >absolutely NO guarantee that it'll get them all right. > >In short, it shouldn't affect the normal user at all. But if you do any >application to application exports / imports, I'd check closer before >dismissing it. > >Joe > >PS ALWAYS watch out for (and double check) the Microsoft PR machine. > >-----Original Message----- >From: Cuny, David [SMTP:David.Cuny at DSS.CA.GOV] >Sent: Wednesday, September 15, 1999 11:45 AM >To: EUPHORIA at LISTSERV.MUOHIO.EDU >Subject: Re: Windows Y2K adjustment > >Mike Sabal wrote: > >> I'm just thinking that there must be a Windows API >> call that actually uses that value; and some programmers >> may errantly use it in some calculations. > >I did a web search when I got the 2/4 digit warning from a friend, and >apparently it's in such wide circulation that Microsoft issued a reaction >to >it. They claimed that it makes no difference, if it makes you feel any >better. > >-- David Cuny >________________________________________________________ >NetZero - We believe in a FREE Internet. Shouldn't you? >Get your FREE Internet Access and Email at >http://www.netzero.net/download/index.html >