 the year 10,000 problem (also known as the y10k problem or the deca-millennium bug) is the class of all potential time formatting and storage bugs that would emerge when the need to express years with five digits arises. the problem can have discernible effects today, but is also sometimes mentioned for humorous effect as in rfc 2550. ==practical relevance== historical and technological trends suggest that in the actual year 10,000 it is practically impossible that any of the data processing technology or software in use today will still be active. however, five-digit years are already a problem today for some forward-looking analysis programs, such as software that examines proposals for the long-term handling of nuclear waste. ==examples== this problem can be seen in the spreadsheet program microsoft excel through at least its office 2013 release, which stores dates as the number of days since 31 december 1899 (day 1 is 1900-01-01); similarly, microsoft access stores dates as the number of days since 30 december 1899 (day 1 is 1899-12-31). in either application, a date value of 2958465 will be correctly formatted as "31 december 9999", but adding 1 to that to step over to the expected date of "1 january 10000" will cause a formatting error; in excel, for example, it will be displayed in the cell as a series of # characters. excel also cannot automatically convert date-formatted strings such as "12/12/2007" to dates if the year exceeds 9999; "12/12/9999" is automatically converted to a date when entered into a cell, but "12/12/10000" is not. the long now foundation ran into this limitation of excel during the design of the 10,000 year clock. sap r/3 handles date variables as strings of 8 characters (yyyymmdd). the open source openoffice.org calc program is able to display dates beyond the year 9999 correctly with five digit years, but at least through version 2.4 falls victim to the year 32,768 problem: "31 december 32,767" is the highest available date it can properly display. 32767, or 215&nbsp;â&nbsp;1, is the highest positive number that can be represented using a 16-bit signed integer, adding one to this value causes it to overflow, and calc interprets the year as a large negative number, "1 january â32,768". the gnu fortran compiler, g77, makes reference in run-time environment limit
10th_millennium Calendars Future_problems Time_formatting_and_storage_bugs