| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Windows CE for Handheld PCs 3.01 (Japanese) - Win CE
| Product Summary |
Product: Windows CE for Handheld PCs
Version: 3.01 |
Category: Compliant#
Operating System: Win CE |
| Language: Japanese |
Release Date: 15 Jan 1999 |
| Operational Range: |
- |
| Prerequisites: |
None |
| Product Dependencies: |
None |
| Clock Dependencies: |
Operating system clock and OLEAUT32 |
| Last Updated: |
29 Jul 1999 | |
| Product Details |
|
Operational Range for Data: OEM dependent.
How the product handles dates:
Windows CE Operating System:
- Storage: Windows CE for the Handheld PC stores a compressed year in the OEM Adaptation Layer, (OAL) which is controlled by an OEM. The date range is therefore hardware specific and is determined by the OEM. OEMs receive sample drivers from Microsoft that contain the default date range (1970-2069). This date range is only for the real-time clock and does not effect date ranges for Windows CE applications. Windows CE for the Handheld PC takes and returns a 4-digit year except in the OAL layer that talks directly to the hardware. External interfaces for the operating system support 4-digit years.
Pocket Excel:
- Storage. Microsoft Excel stores dates as numeric values, with day #1 being 1900/1/1. Excel 97 recognizes 01-JAN-1900 through 31-DEC-9999 as valid dates.
- Formatting. When Microsoft Excel formats a date, it uses one of several default formats. If the system short date in Control Panel | Regional Settings is set to YY format (YY refers to a 2-digit year entry), then all dates will by default display in a YY format - even when the user types a YYYY date (4-digit year entry).
- Parsing on date entry. If a user enters a date in a "yy/mm/dd" or "yy-m-d" format, it will be interpreted as a Japanese era date. For instance, "1/2/3" will parse to 03 FEB 1989, or February 3, Heisei year 1. To avoid ambiguity, enter dates in a YYYY/MM/DD format so they can be clearly understood as Gregorian dates. Or enter dates with a prefix for the Japanese era, such as H, S, T, or M, so they can be understood as Japanese era dates.
Note: If a user enters a date that can be interpreted in both "mm/dd/yy" and "yy/mm/dd" formats, then the date will default to the "yy/mm/dd" format. To avoid ambiguity, enter dates in a YYYY/MM/DD format so the date can be clearly understood.
- Leap Year. Microsoft Pocket Excel treats 1900 as a leap year for backward compatibility with other products.
- String date parsing during calculations. If a formula takes a string date as an argument, the string date is currently parsed using the same code as the date entry shown above in "Parsing on date entry."
Pocket Word:
- Storage: Date and time values for date usage in Pocket Word are stored as simple text strings.
Pocket PowerPoint:
- Storage: Date and time values for date usage in Pocket PowerPoint are stored as simple text strings
Pocket Access
- Storage: The supported date range is 1/1/1601 through 12/31/9999.
Dates are stored internally as Win32 FILETIME structures.
- Parsing on date entry. Dates are parsed using OLE Automation.
- How OLE Automation Technology handles dates: When a string containing a date is converted into a date type, the conversion initially uses the rules specified in the control panel regional setting for short dates. This is very important since different locales have widely different date formats. If this fails, OLE-Automation logic attempts to make sense of the date that has been entered. The assumption made throughout this process is that the user has entered a valid date and therefore OLE-Automation will attempt to interpret it.
- Two-digit shortcut handling: Pocket Access interprets dates entered with a
2-digit shortcut in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999
Inbox:
- Storage: Dates are stored internally as Win32 FILETIME structures. The system clock is used for current date and time data.
- Formatting. Dates are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet.
- Date Display: Dates are displayed in listview and readview, but not in sendview.
- SMTP/POP3 Transport: The POP3 transport translates 2-digit and 4-digit year dates on incoming messages into Win32 FILETIME structures. Incoming 2-digit year dates will use the current century for the translation into Win32 FILETIME structures.
- IMAP4: The IMAP4 transport translates 4-digit year dates on incoming messages into Win32 FILETIME structures.
- TNEF Parsing: Reads dates on incoming Schedule + messages. Dates in property format are stored in Win32 FILETIME format (inside a binary file, which are extracted from the text of the message).
Pocket Internet Explorer:
- Storage: Dates are stored internally as Win32 FILETIME structures. There are three main areas where Pocket Internet Explorer receives dates from the outside world: Cookies, FTP listings, and Security Certificates. A 2-digit year that is less than 79 is interpreted as 20XX. A 2-digit year that is greater than or equal to 80 is interpreted as 19XX.
PIM:
- Storage: Two digit dates are not stored in the year field of any data structures. Various types of structures, such as FILETIME, SYSTEMTIME, YMD (a shorter version of SYSTEMTIME), and RTime (which is the relative date since 1/1/1601) are used to store dates. The PIM applications can handle dates from 1850 until 2399.
- Formatting: Years are displayed in 2-digit and 4-digit formats, using the short and long date formats specified in the Regional Settings applet in Control Panel. Date entry fields parse and accept inputs that follow the formats specified in the Regional Settings applet. In any case where years are displayed in the 2-digit format, GetDateFormat is used to format the date.
2-digit shortcut handling:
Windows CE operating system:
- Windows CE does not contain 2-digit conversion logic but OLE does. OLE converts a 2-digit date to a 4-digit date using the following rules:
00-29 convert to 2000-2029
30-99 convert to 1930-1999
See the OLE DB compliance document for additional information.
Common date usage errors:
Windows CE:
- Windows CE is dependent upon the OEM and their implementation of the OEM's real-time clock Application Programming Interfaces (APIs). The OEM must provide the correct information in their OAL/hardware to maintain proper date handling.
Pocket Excel:
- The DATE() function is not designed to take 2-digit year shortcuts, since it receives numeric parameters. The DATE() function calculates a number less than 1900 as an offset from 1900. So, if a formula such as =DATE(15,1,1) were entered, the resulting date would be January 1, 1915, not 2015.
- Using a format such as "Dec 98", which is not fully distinguished, will not function correctly at the year 2001. This is because 98 is too large to be the day of month so Microsoft Pocket Excel assumes it is a year. However, Microsoft Pocket Excel assumes "Dec 01" refers to December 1 of the current year, as 01 is small enough to be interpreted as a day of the month.
- Due to the ambiguous nature of text dates, in general they will have some potential for error. Use serial dates whenever possible and take great care when transferring text dates.
- Change the default system short date format to include a 4-digit year. Get in the habit of using 4-digit year formats for dates in Microsoft Pocket Excel. Such a practice will make the date visible if a user mistakenly enters a date in the wrong century. When dates must be transferred between applications, ideally they should be transferred as serial dates. They should not be transferred as an ambiguous text format that doesn't specify the century and causes confusion between month and day-of-month. For example, the text "25/2/1" could be interpreted as Feb. 1, 1925, Jan. 2, 1925, Feb. 1, 2025, or Jan. 2, 2025.
- Defined names store references as text strings. Since they do not store dates as serial values, they are susceptible to century issues when a 2-digit format is used for the year. Using defined names in this way is also problematic because users who use a date format with an order other than M-d-y will experience misinterpretations. Recommended usage is to define the name referring to a cell containing a serial date, which will avoid both of the above-mentioned potential problems.
Issues to be aware of when developing applications for Windows CE for Handheld PC Professional Edition:
- The number of digits specified for a dateÆs century can be either 2 or 4 (e.g., 98 or 1998). This information is returned when GetLocaleInfo is used to request LOCALE_ICENTURY. The results of a request for the century information is based on the following:
- If the default value has not been overridden then the value returned is the default for the locale. The value returned by LOCAL_ICENTURY is based on the format of the default short date (LOCALE_SSHORTDATE). If the format of the short date is "yy" then a 2-digit century format is specified otherwise if the format is "yyyy" then a 4-digit century format is specified.
- If SetLocaleInfo is used with LOCALE_ICENTURY to change (override) the current default century format from a 2-digit to a 4-digit century format or vice versa.
The LOCAL_ICENTURY value for the current short date format is not updated to reflect the current century information if:
- The Regional Control Panel is used to change the default short date format from a 4-digit year to a 2-digit year, or vice versa.
- Using SetLocaleInfo(LOCALE_SSHORTDATE) the default short date format is changed from a 4-digit year to a 2-digit year, or vice versa.
In both cases the value returned for LOCALE_ICENTURY is the same as before the date format was changed. To compensate for this an application can retrieve the short date format and count the number of æyÆs that are in the year format.
| |
Return to Search Screen
| Legend of Symbols: |
| * |
The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document. |
| # |
The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product. |
| + |
The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details. |
| Note: Compliance ratings given for each product assume that all recommended actions have been taken. |
If after reviewing this information you have additional questions related to this product, click here.
YEAR 2000 READINESS DISCLOSURE
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.
ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
