Product Summary
Product: RDS	Version: 1.5	Category:Compliant
Language: Slovenian	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1997 RDS 1.5 shipped with Internet Information Server How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 1.5	Category:Compliant
Language: Spanish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1997 RDS 1.5 shipped with Internet Information Server How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 1.5	Category:Compliant
Language: Swedish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1997 RDS 1.5 shipped with Internet Information Server How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 1.5	Category:Compliant
Language: Turkish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1997 RDS 1.5 shipped with Internet Information Server How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: French	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: Italian	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	22 Feb 1999
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 6.0. How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: RDS	Version: 2.0	Category:Compliant
Language: Spanish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows NT or Windows 95, Internet Explorer 3.02 or Internet Explorer 4.01, Windows NT Option Pack: Internet Information Server 3.0 or 4.0, DCOM, ADO, OLEDB, ODBC
Clock Dependencies:	none
Last Updated:	12 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent Release Date: 1998 RDS 2.0 shipped with Visual Studio 98 How the product handles dates: RDS internally stores, compares, and sequences dates in 4-digit format. Supported date formats are DATE, DBDATE, and DBTIMESTAMP. Each of these formats handles dates beyond the year 2035. Two-digit shortcut handling: This functionality is provided through OLE DB via OLEAUT32.DLL date conversions. Common date usage errors: Developers may set up their database schema for 2-digit storage or may use 2-digit variables in their ADO and Visual Basic code. Testing guidelines and recommendations: Use 4-digit dates throughout projects that use ADO/RDS and OLE DB.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Return of Arcade	Version: 1.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 30 Mar 1996
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows 95, Windows 98
Clock Dependencies:	none
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: This product does not examine dates or handle information that includes dates. Two-digit shortcut handling: Not Applicable. Common date usage errors: None. Testing guidelines and recommendations: None. Note: Return of Arcade will refuse to install on Windows NT or Windows 2000. It requires Windows 95 or Windows 98.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Return of Arcade	Version: 1.0	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: 30 Mar 1996
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows 95, Windows 98
Clock Dependencies:	none
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: This product does not examine dates or handle information that includes dates. Two-digit shortcut handling: Not Applicable. Common date usage errors: None. Testing guidelines and recommendations: None. Note: Return of Arcade will refuse to install on Windows NT or Windows 2000. It requires Windows 95 or Windows 98.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Revenge of Arcade	Version: 1.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 02 Jun 1998
Operational Range:	-
Prerequisites:	None
Product Dependencies:	None
Clock Dependencies:	None
Last Updated:	10 Sep 1999
Product Details
How the product handles dates: Revenge of the Arcade does not handle dates or perform two-digit shortcut interpretations.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Routing & Remote Access Services	Version:	Category:Compliant*
Language: English	OS: Win NT	Release Date: N/A
Operational Range:	-
Prerequisites:	Windows NT 4.0 SP4
Product Dependencies:
Clock Dependencies:
Last Updated:	26 Aug 1999
Product Details
This component is an integral part of Windows NT Server. Click here to go to the Windows NT 4, sp4 compliance document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Chinese - Simplified	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 3.1x,
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Winows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Chinese - Traditional	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Winows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Czech	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Danish	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Dutch	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: English	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	NONE
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Finnish	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: French	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	NONE
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: German	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	NONE
Product Dependencies:	Windows 3.1x, Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Hungarian	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Italian	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	16 Aug 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Japanese	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Winows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Korean	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Norwegian	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Polish	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Portuguese (Brazil)	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Portuguese	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Russian	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Spanish	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.0x	Category:Compliant#
Language: Swedish	OS: 16-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	none
Product Dependencies:	Windows 3.1x
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Description of how the product handles dates: Storage.  All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data.  Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates.   Two-digit shortcut handling: When the system clock's short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application's user interface allows only 2-digit entries.  All such entries are parsed into 1980 through 2079. When the system clock's short date format is set to display a 4-digit year, the application's user interface allows only 4-digit entries.  Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system's short date format to mm/dd/yyyy.  The application's user interface shows a 4-digit entry box for years.  The user types in only a 2-digit "23".  In the user interface, the user sees "0023" because they did not fill in the other 2 digits.  When they <tab> off the field, they see that the application turns the "0023" into "1923".  If this is not the year the user intended, they can then change it by typing in all 4 digits.  All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel).  If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits.  Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back.  In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000.  They should then let the system clocks roll over to the year 2000.  All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Arabic	OS: 32-Bit Win	Release Date: 01 Jul 1996
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Czech	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Danish	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Dutch	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant*
Language: English	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	Schedule+ Year 2000 Software Update
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	29 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Prerequisites Download the Schedule+ Year 2000 Software Update available at http://support.microsoft.com/support/kb/articles/q197/1/95.asp. Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Finnish	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: French	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: German	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Hebrew	OS: 32-Bit Win	Release Date: 01 Jul 1996
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Hungarian	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Italian	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 9999
Prerequisites:	none
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Japanese	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Schedule +	Version: 7.5	Category:Compliant#
Language: Korean	OS: 32-Bit Win	Release Date: 01 Aug 1995
Operational Range:	01 Jan 1900 - 31 Dec 2999
Prerequisites:	None
Product Dependencies:	Windows 95, Windows NT 3.51, or Windows NT 4.0
Clock Dependencies:	Operating System Clock
Last Updated:	07 Jul 1999
Product Details
Operating system: Windows 3.x, Windows 95, Windows NT Description of how the product handles dates: Storage. All dates in Microsoft Schedule+ are stored as sixteen bit integers, never with a two-digit year value. In all instances the system clock is used for current date and time data. Schedule+ uses the display options set under Regional Settings in the Windows Control Panel to determine the display and entry mode for dates. Two-digit shortcut handling: When the system clock’s short date format (Control Panel Regional Settings) is set to display a 2-digit year, the application’s user interface allows only 2-digit entries. All such entries are parsed into 1980 through 2079. When the system clock’s short date format is set to display a 4-digit year, the application’s user interface allows only 4-digit entries. Under such setting, if the user types in a 4-digit entry, there is no ambiguity. But if the user types in a 2-digit entry with the user interface prompting for a 4-digit year, those 2-digit entries will become 19xx. For example, the user sets the system’s short date format to mm/dd/yyyy. The application’s user interface shows a 4-digit entry box for years. The user types in only a 2-digit "23". In the user interface, the user sees "0023" because they did not fill in the other 2 digits. When they <tab> off the field, they see that the application turns the "0023" into "1923". If this is not the year the user intended, they can then change it by typing in all 4 digits. All of this is displayed in the user interface so it does not mislead the user into thinking the 2-digit entry meant something else. Note that all of the above explanation applies only when a user types in a 2-digit entry while being prompted for a 4-digit one (as set in Control Panel). If the Control Panel system setting is set to use a 2-digit year for short dates, which is the operating system default, year entries are always parsed to 1980 through 2079. Common date usage errors: Two-digit shortcuts are supported past the year 2000 only if the date display option for Regional Settings in the Control Panel of the operating system is set for two digits. Microsoft recommends use with display of full four digits, suspending two-digit entry. Testing guidelines and recommendations: In general, avoid testing in a production environment because side effects with other products cannot be predicted. Note that reminders for future appointments may be set off during this testing and will not re-notify when date is set back. In testing this product, customers should set server and client clocks to December 31st, 1999, then add and modify various appointments, tasks, and events that are in the year 1999 as well as in the future past January 1st, 2000. They should then let the system clocks roll over to the year 2000. All reminders and appointment/task/event manipulations should function correctly, both before and after the rollover.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.