Product Summary
Product: Close Combat: A Bridge Too Far	Version: 2.0b	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 24 Sep 1997
Operational Range:	24 Sep 1997 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	DirectX 5.0, DXMedia, Acrobat 3.0
Clock Dependencies:	System Clock (but not accessed by our application or setup)
Last Updated:	22 Jun 1999
Product Details
How the product handles dates: Not Applicable as the product does not intrinsically use dates. Two-digit shortcut handling: Not Applicable.

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: Close Combat: A Bridge Too Far	Version: 2.0b	Category:Compliant
Language: French	OS: 32-Bit Win	Release Date: 24 Sep 1997
Operational Range:	24 Sep 1997 - 31 Dec 2035
Prerequisites:	None
Product Dependencies:	DirectX 5.0, DXMedia, Acrobat 3.0
Clock Dependencies:	System Clock (but not accessed by our application or setup)
Last Updated:	22 Jun 1999
Product Details
Note: Only manuals have been translated. How the product handles dates: Not Applicable as the product does not intrinsically use dates. Two-digit shortcut handling: Not Applicable.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: French	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: Italian	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
Note: Only the manual was localized. How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: Portuguese (Brazil)	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
Note: Only the manual was localized. How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Combat Flight Simulator	Version: 1.0	Category:Compliant
Language: Spanish	OS: 32-Bit Win	Release Date: 07 Oct 1998
Operational Range:	-
Prerequisites:
Product Dependencies:	Win95 or later; Windows NT SP3 or later
Clock Dependencies:
Last Updated:	07 Jul 1999
Product Details
Note: Only the manual was localized. How the product handles dates: Pilot log for Combat Flight Simulator is stored in a four-digit format.

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: Commercial Internet System	Version: 2.0	Category:Compliant#
Language: English	OS: Win NT	Release Date: 01 Aug 1998
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	None
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.01
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
How the product handles dates: Connection Manager The only area where Connection Manger interacts with date related data is in performing counter operations. This is done using seconds from 1970. There are no areas where Connection Manager users input, save, or manipulate dates. Connection Manager Administration Kit Connection Manager Administration Kit uses no date related data. Connection Point Services Connection Point Services uses date released data in the following manners: The PBA tool date stamps phone book changes and logs them to a log file. The latest entry date from the log is presented to the user in a system defined format (mm-dd-yy by default). When doing phone book posting, the phone book server does a date comparison of the "live" phone book with the updated newpbk.mdb. It then proceeds to update itself if newpbk.mdb is newer than the live version. Internet Authentication Service (IAS) and IAS Commercial Edition There are three areas where IAS interacts with date related data: RADIUS attribute based on date and time of day – the attribute data type is specified in RFC to be 32-bit and having no known year 2000 issues. Accounting log file names are in yyyymmdd log format. IAS gets the date from the operating system and uses 4-digit years. Accounting record logs date in mm/dd/yyyy format. IAS gets the date from the operating system and uses 4-digit years. Internet Mail, News, and Chat CDONTS: CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2 digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The date used for the headers are 4 digits with no known year 2000 issues, but the RFC 822 message headers only use the last 2 digits for the year date. Chat Server: The Chat Server calculates time based on tick counts for real time collaboration, which do not span across a year period. When dates are kept, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits. IMC: The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the file system (NTFS). RFC 822 messages store date formats with 2-digits representing the year. Site Server 3.0, Commerce Edition For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900 and December 31, 2078. For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753, to December 31, 9999. Commerce Server: the product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are converted with the full 4-digit year. See separately available year 2000 compliance documentation for Site Server 3.0, Commerce Edition. SQL Server 6.5 – see separately available year 2000 product guide documentation for SQL Server 6.5.   Two-digit shortcut handling: Connection Point Services Connection Point Services doesn't handle dates with its log files. It stores, retrieves, and displays a date. It stores and displays the year in a 2-digit format (YY) or 4-digit format (YYYY) based on system regional settings. Two-digit years are displayed when system settings call for 4-digit display (YYYY). After year 2029, Connection Point Services uses the 4-digit format. Internet Authentication Service (IAS) and IAS Commercial Edition No two-digit short cut handling is used in Internet Authentication Service. Site Server 3.0, Commerce Edition With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format. The Web Admin will not accept a date with a 2-digit year. In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy". With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4. Membership Directory Manager supports dates in 2-digit shortcuts. With the Membership Directory Manager the logic is the same as for Internet Explorer 4.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. Commerce––OLE Automation calls make most of the conversions. The product does have a private DataFunctions object that does the conversion in some cases, but this object also relies on OLE Automation calls. Ad System––Server code uses 4-digit only. The Ad Manager code uses the same DataFunctions as Commerce Server 3.0, as well as some native SQL-provided conversion routines ({ts} as an example). Common date usage errors: See comments for Site Server 3.0, Commerce Edition. Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. Ad System––Although not really an SDK, users have the ability to modify the Ad Manager pages in the product, leading to potential year 2000 problems. To avoid problems, users should refrain from modifying pages in the product.   Testing guidelines and recommendations: Since most Commerce sites are web-based applications, it is important to verify any interface with the user and the HTML/ASL code written to handle this interaction. Store authors need to verify that the parts they author are compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To change this, change the HTML. In general, avoid testing in a production environment or with non-duplicated production files because side effects with other products are difficult to predict.   Site Server 3 Testing Instructions Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Commercial Internet System. It is recommended that testing be done on non-productions systems. Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues. Also, start replication between servers just prior to midnight, December 31, 1999. Add members to Membership Groups with expiration date set to right before and after January 1, 2000. Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.

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: Commercial Internet System	Version: 2.0	Category:Compliant#
Language: French	OS: Win NT	Release Date: 01 Aug 1998
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	None
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.01
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
How the product handles dates: Connection Manager The only area where Connection Manger interacts with date related data is in performing counter operations. This is done using seconds from 1970. There are no areas where Connection Manager users input, save, or manipulate dates. Connection Manager Administration Kit Connection Manager Administration Kit uses no date related data. Connection Point Services Connection Point Services uses date released data in the following manners: The PBA tool date stamps phone book changes and logs them to a log file. The latest entry date from the log is presented to the user in a system defined format (mm-dd-yy by default). When doing phone book posting, the phone book server does a date comparison of the "live" phone book with the updated newpbk.mdb. It then proceeds to update itself if newpbk.mdb is newer than the live version. Internet Authentication Service (IAS) and IAS Commercial Edition There are three areas where IAS interacts with date related data: RADIUS attribute based on date and time of day – the attribute data type is specified in RFC to be 32-bit and having no known year 2000 issues. Accounting log file names are in yyyymmdd log format. IAS gets the date from the operating system and uses 4-digit years. Accounting record logs date in mm/dd/yyyy format. IAS gets the date from the operating system and uses 4-digit years. Internet Mail, News, and Chat CDONTS: CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2 digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The date used for the headers are 4 digits with no known year 2000 issues, but the RFC 822 message headers only use the last 2 digits for the year date. Chat Server: The Chat Server calculates time based on tick counts for real time collaboration, which do not span across a year period. When dates are kept, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits. IMC: The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the file system (NTFS). RFC 822 messages store date formats with 2-digits representing the year. Site Server 3.0, Commerce Edition For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900 and December 31, 2078. For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753, to December 31, 9999. Commerce Server: the product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are converted with the full 4-digit year. See separately available year 2000 compliance documentation for Site Server 3.0, Commerce Edition. SQL Server 6.5 – see separately available year 2000 product guide documentation for SQL Server 6.5.   Two-digit shortcut handling: Connection Point Services Connection Point Services doesn't handle dates with its log files. It stores, retrieves, and displays a date. It stores and displays the year in a 2-digit format (YY) or 4-digit format (YYYY) based on system regional settings. Two-digit years are displayed when system settings call for 4-digit display (YYYY). After year 2029, Connection Point Services uses the 4-digit format. Internet Authentication Service (IAS) and IAS Commercial Edition No two-digit short cut handling is used in Internet Authentication Service. Site Server 3.0, Commerce Edition With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format. The Web Admin will not accept a date with a 2-digit year. In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy". With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4. Membership Directory Manager supports dates in 2-digit shortcuts. With the Membership Directory Manager the logic is the same as for Internet Explorer 4.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. Commerce––OLE Automation calls make most of the conversions. The product does have a private DataFunctions object that does the conversion in some cases, but this object also relies on OLE Automation calls. Ad System––Server code uses 4-digit only. The Ad Manager code uses the same DataFunctions as Commerce Server 3.0, as well as some native SQL-provided conversion routines ({ts} as an example). Common date usage errors: See comments for Site Server 3.0, Commerce Edition. Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. Ad System––Although not really an SDK, users have the ability to modify the Ad Manager pages in the product, leading to potential year 2000 problems. To avoid problems, users should refrain from modifying pages in the product.   Testing guidelines and recommendations: Since most Commerce sites are web-based applications, it is important to verify any interface with the user and the HTML/ASL code written to handle this interaction. Store authors need to verify that the parts they author are compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To change this, change the HTML. In general, avoid testing in a production environment or with non-duplicated production files because side effects with other products are difficult to predict.   Site Server 3 Testing Instructions Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Commercial Internet System. It is recommended that testing be done on non-productions systems. Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues. Also, start replication between servers just prior to midnight, December 31, 1999. Add members to Membership Groups with expiration date set to right before and after January 1, 2000. Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.

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: Commercial Internet System	Version: 2.0	Category:Compliant#
Language: German	OS: Win NT	Release Date: 01 Aug 1998
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	None
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.01
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
How the product handles dates: Connection Manager The only area where Connection Manger interacts with date related data is in performing counter operations. This is done using seconds from 1970. There are no areas where Connection Manager users input, save, or manipulate dates. Connection Manager Administration Kit Connection Manager Administration Kit uses no date related data. Connection Point Services Connection Point Services uses date released data in the following manners: The PBA tool date stamps phone book changes and logs them to a log file. The latest entry date from the log is presented to the user in a system defined format (mm-dd-yy by default). When doing phone book posting, the phone book server does a date comparison of the "live" phone book with the updated newpbk.mdb. It then proceeds to update itself if newpbk.mdb is newer than the live version. Internet Authentication Service (IAS) and IAS Commercial Edition There are three areas where IAS interacts with date related data: RADIUS attribute based on date and time of day – the attribute data type is specified in RFC to be 32-bit and having no known year 2000 issues. Accounting log file names are in yyyymmdd log format. IAS gets the date from the operating system and uses 4-digit years. Accounting record logs date in mm/dd/yyyy format. IAS gets the date from the operating system and uses 4-digit years. Internet Mail, News, and Chat CDONTS: CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2 digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The date used for the headers are 4 digits with no known year 2000 issues, but the RFC 822 message headers only use the last 2 digits for the year date. Chat Server: The Chat Server calculates time based on tick counts for real time collaboration, which do not span across a year period. When dates are kept, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits. IMC: The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the file system (NTFS). RFC 822 messages store date formats with 2-digits representing the year. Site Server 3.0, Commerce Edition For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900 and December 31, 2078. For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753, to December 31, 9999. Commerce Server: the product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are converted with the full 4-digit year. See separately available year 2000 compliance documentation for Site Server 3.0, Commerce Edition. SQL Server 6.5 – see separately available year 2000 product guide documentation for SQL Server 6.5.   Two-digit shortcut handling: Connection Point Services Connection Point Services doesn't handle dates with its log files. It stores, retrieves, and displays a date. It stores and displays the year in a 2-digit format (YY) or 4-digit format (YYYY) based on system regional settings. Two-digit years are displayed when system settings call for 4-digit display (YYYY). After year 2029, Connection Point Services uses the 4-digit format. Internet Authentication Service (IAS) and IAS Commercial Edition No two-digit short cut handling is used in Internet Authentication Service. Site Server 3.0, Commerce Edition With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format. The Web Admin will not accept a date with a 2-digit year. In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy". With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4. Membership Directory Manager supports dates in 2-digit shortcuts. With the Membership Directory Manager the logic is the same as for Internet Explorer 4.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. Commerce––OLE Automation calls make most of the conversions. The product does have a private DataFunctions object that does the conversion in some cases, but this object also relies on OLE Automation calls. Ad System––Server code uses 4-digit only. The Ad Manager code uses the same DataFunctions as Commerce Server 3.0, as well as some native SQL-provided conversion routines ({ts} as an example). Common date usage errors: See comments for Site Server 3.0, Commerce Edition. Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. Ad System––Although not really an SDK, users have the ability to modify the Ad Manager pages in the product, leading to potential year 2000 problems. To avoid problems, users should refrain from modifying pages in the product.   Testing guidelines and recommendations: Since most Commerce sites are web-based applications, it is important to verify any interface with the user and the HTML/ASL code written to handle this interaction. Store authors need to verify that the parts they author are compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To change this, change the HTML. In general, avoid testing in a production environment or with non-duplicated production files because side effects with other products are difficult to predict.   Site Server 3 Testing Instructions Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Commercial Internet System. It is recommended that testing be done on non-productions systems. Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues. Also, start replication between servers just prior to midnight, December 31, 1999. Add members to Membership Groups with expiration date set to right before and after January 1, 2000. Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.

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: Commercial Internet System	Version: 2.0	Category:Compliant#
Language: Japanese	OS: Win NT	Release Date: 01 Oct 1998
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	None
Product Dependencies:	Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.01 or later
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
How the product handles dates: Connection Manager The only area where Connection Manger interacts with date related data is in performing counter operations. This is done using seconds from 1970. There are no areas where Connection Manager users input, save, or manipulate dates. Connection Manager Administration Kit Connection Manager Administration Kit uses no date related data. Connection Point Services Connection Point Services uses date released data in the following manners: The PBA tool date stamps phone book changes and logs them to a log file. The latest entry date from the log is presented to the user in a system defined format (mm-dd-yy by default). When doing phone book posting, the phone book server does a date comparison of the "live" phone book with the updated newpbk.mdb. It then proceeds to update itself if newpbk.mdb is newer than the live version. Internet Authentication Service (IAS) and IAS Commercial Edition There are three areas where IAS interacts with date related data: RADIUS attribute based on date and time of day – the attribute data type is specified in RFC to be 32-bit and having no known year 2000 issues. Accounting log file names are in yyyymmdd log format. IAS gets the date from the operating system and uses 4-digit years. Accounting record logs date in mm/dd/yyyy format. IAS gets the date from the operating system and uses 4-digit years. Internet Mail, News, and Chat CDONTS: CDONTS and the protocol stacks (NNTP and SMTP) support RFC 822 messages. This message format uses 2 digits to represent the year within the date header information. Date properties exposed by CDONTS are read-only and based on the FILETIME data structure. Outbound messages are stamped with the current system time using the operating system clock. The date used for the headers are 4 digits with no known year 2000 issues, but the RFC 822 message headers only use the last 2 digits for the year date. Chat Server: The Chat Server calculates time based on tick counts for real time collaboration, which do not span across a year period. When dates are kept, the Chat server will store the date using a large integer, which allows the year to be stored with 4 digits. IMC: The IMC stores dates internally as a FILETIME structure. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. Messages that are of the format RFC 822, that come into the IMC, are handled by IMAIL and the file system (NTFS). RFC 822 messages store date formats with 2-digits representing the year. Site Server 3.0, Commerce Edition For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900 and December 31, 2078. For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753, to December 31, 9999. Commerce Server: the product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are converted with the full 4-digit year. See separately available year 2000 compliance documentation for Site Server 3.0, Commerce Edition. SQL Server 6.5 – see separately available year 2000 product guide documentation for SQL Server 6.5.   Two-digit shortcut handling: Connection Point Services Connection Point Services doesn't handle dates with its log files. It stores, retrieves, and displays a date. It stores and displays the year in a 2-digit format (YY) or 4-digit format (YYYY) based on system regional settings. Two-digit years are displayed when system settings call for 4-digit display (YYYY). After year 2029, Connection Point Services uses the 4-digit format. Internet Authentication Service (IAS) and IAS Commercial Edition No two-digit short cut handling is used in Internet Authentication Service. Site Server 3.0, Commerce Edition With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format. The Web Admin will not accept a date with a 2-digit year. In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy". With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4. Membership Directory Manager supports dates in 2-digit shortcuts. With the Membership Directory Manager the logic is the same as for Internet Explorer 4.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. Commerce––OLE Automation calls make most of the conversions. The product does have a private DataFunctions object that does the conversion in some cases, but this object also relies on OLE Automation calls. Ad System––Server code uses 4-digit only. The Ad Manager code uses the same DataFunctions as Commerce Server 3.0, as well as some native SQL-provided conversion routines ({ts} as an example). Common date usage errors: See comments for Site Server 3.0, Commerce Edition. Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. Ad System––Although not really an SDK, users have the ability to modify the Ad Manager pages in the product, leading to potential year 2000 problems. To avoid problems, users should refrain from modifying pages in the product.   Testing guidelines and recommendations: Since most Commerce sites are web-based applications, it is important to verify any interface with the user and the HTML/ASL code written to handle this interaction. Store authors need to verify that the parts they author are compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To change this, change the HTML. In general, avoid testing in a production environment or with non-duplicated production files because side effects with other products are difficult to predict.   Site Server 3 Testing Instructions Microsoft understands that for various reasons customers may be required to conduct their own year 2000 certification testing. Microsoft provides the tests below to aid customers in conducting their own year 2000 certification of Microsoft Commercial Internet System. It is recommended that testing be done on non-productions systems. Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues. Also, start replication between servers just prior to midnight, December 31, 1999. Add members to Membership Groups with expiration date set to right before and after January 1, 2000. Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.

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: Commercial Internet System	Version: 2.5	Category:Compliant*
Language: English	OS: Win NT	Release Date: 18 May 1999
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	Windows NT 4.0 Service Pack 4 or greater, Site Server 3 Service Pack 2, Windows NT Option Pack, SQL Server 6.5 Service Pack 5
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 5, SQL Server 6.5 with Service Pack 5 or SQL Server 7.0, Site Server 3 with Service Pack 2, Commercial Internet System 2.0.
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
Microsoft Commercial Internet System (MCIS) 2.5 How the product handles dates: Please read the Year 2000 disclosure statement for Commercial Internet System 2.0 carefully. This document covers only those features that are provided with MCIS 2.5 and does not cover any features or components of MCIS 2.0. MCIS Administration and Provisioning Services 2.5 (MAPS) There are only two functions for which MAPS does date handling: credit card expiration and transaction time-stamping MAPS transaction time-stamping leverages the Microsoft SQL Server 6.5 or 7.0 datetime data type. Please see the disclosure statement for SQL Server 6.5 and 7.0 for more information. HTML Mail Interface (HMI) The only date handling in HMI exists in the Collaboration Data Objects. This functionality supplies date information for the RFC 822 header. This RFC requires a 4-digit date and Collaboration Data Objects has no known issues with that standard. There is no other date handling in HMI. Personal Web Pages (PWP) There is no date/time handling in PWP beyond what exists in Internet Information Server 4.0. Internet Information Server 4.0has no known issues. Simple Network Management Protocol Management Information Bases (SNMP MIBs) There is no date/time handling in the SNMP MIBs other than what is provided in the Windows NT 4.0 SNMP service.   Two-digit shortcut handling: Commercial Internet System 2.5 does not use 2-digit shortcuts. Common date usage errors: Site Server 3.0 Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.

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: Commercial Internet System	Version: 2.5	Category:Compliant*
Language: French	OS: Win NT	Release Date: 18 May 1999
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	Windows NT 4.0 Service Pack 4 or greater, Site Server 3 Service Pack 2, Windows NT Option Pack, SQL Server 6.5 Service Pack 5
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 5, SQL Server 6.5 with Service Pack 5 or SQL Server 7.0, Site Server 3 with Service Pack 2, Commercial Internet System 2.0.
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
Microsoft Commercial Internet System (MCIS) 2.5 How the product handles dates: Please read the Year 2000 disclosure statement for Commercial Internet System 2.0 carefully. This document covers only those features that are provided with MCIS 2.5 and does not cover any features or components of MCIS 2.0. MCIS Administration and Provisioning Services 2.5 (MAPS) There are only two functions for which MAPS does date handling: credit card expiration and transaction time-stamping MAPS transaction time-stamping leverages the Microsoft SQL Server 6.5 or 7.0 datetime data type. Please see the disclosure statement for SQL Server 6.5 and 7.0 for more information. HTML Mail Interface (HMI) The only date handling in HMI exists in the Collaboration Data Objects. This functionality supplies date information for the RFC 822 header. This RFC requires a 4-digit date and Collaboration Data Objects has no known issues with that standard. There is no other date handling in HMI. Personal Web Pages (PWP) There is no date/time handling in PWP beyond what exists in Internet Information Server 4.0. Internet Information Server 4.0has no known issues. Simple Network Management Protocol Management Information Bases (SNMP MIBs) There is no date/time handling in the SNMP MIBs other than what is provided in the Windows NT 4.0 SNMP service.   Two-digit shortcut handling: Commercial Internet System 2.5 does not use 2-digit shortcuts. Common date usage errors: Site Server 3.0 Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.

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: Commercial Internet System	Version: 2.5	Category:Compliant*
Language: German	OS: Win NT	Release Date: 18 May 1999
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	Windows NT 4.0 Service Pack 4 or greater, Site Server 3 Service Pack 2, Windows NT Option Pack, SQL Server 6.5 Service Pack 5
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 5, SQL Server 6.5 with Service Pack 5 or SQL Server 7.0, Site Server 3 with Service Pack 2, Commercial Internet System 2.0.
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
Microsoft Commercial Internet System (MCIS) 2.5 How the product handles dates: Please read the Year 2000 disclosure statement for Commercial Internet System 2.0 carefully. This document covers only those features that are provided with MCIS 2.5 and does not cover any features or components of MCIS 2.0. MCIS Administration and Provisioning Services 2.5 (MAPS) There are only two functions for which MAPS does date handling: credit card expiration and transaction time-stamping MAPS transaction time-stamping leverages the Microsoft SQL Server 6.5 or 7.0 datetime data type. Please see the disclosure statement for SQL Server 6.5 and 7.0 for more information. HTML Mail Interface (HMI) The only date handling in HMI exists in the Collaboration Data Objects. This functionality supplies date information for the RFC 822 header. This RFC requires a 4-digit date and Collaboration Data Objects has no known issues with that standard. There is no other date handling in HMI. Personal Web Pages (PWP) There is no date/time handling in PWP beyond what exists in Internet Information Server 4.0. Internet Information Server 4.0has no known issues. Simple Network Management Protocol Management Information Bases (SNMP MIBs) There is no date/time handling in the SNMP MIBs other than what is provided in the Windows NT 4.0 SNMP service.   Two-digit shortcut handling: Commercial Internet System 2.5 does not use 2-digit shortcuts. Common date usage errors: Site Server 3.0 Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.

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: Commercial Internet System	Version: 2.5	Category:Compliant*
Language: Japanese	OS: Win NT	Release Date: 01 Oct 1999
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	Windows NT 4.0 Service Pack 4 or greater, Site Server 3 Service Pack 2, Windows NT Option Pack, SQL Server 6.5 Service Pack 5
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 5, SQL Server 6.5 with Service Pack 5 or SQL Server 7.0, Site Server 3 with Service Pack 2, Commercial Internet System 2.0.
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
Microsoft Commercial Internet System (MCIS) 2.5 How the product handles dates: Please read the Year 2000 disclosure statement for Commercial Internet System 2.0 carefully. This document covers only those features that are provided with MCIS 2.5 and does not cover any features or components of MCIS 2.0. MCIS Administration and Provisioning Services 2.5 (MAPS) There are only two functions for which MAPS does date handling: credit card expiration and transaction time-stamping MAPS transaction time-stamping leverages the Microsoft SQL Server 6.5 or 7.0 datetime data type. Please see the disclosure statement for SQL Server 6.5 and 7.0 for more information. HTML Mail Interface (HMI) The only date handling in HMI exists in the Collaboration Data Objects. This functionality supplies date information for the RFC 822 header. This RFC requires a 4-digit date and Collaboration Data Objects has no known issues with that standard. There is no other date handling in HMI. Personal Web Pages (PWP) There is no date/time handling in PWP beyond what exists in Internet Information Server 4.0. Internet Information Server 4.0has no known issues. Simple Network Management Protocol Management Information Bases (SNMP MIBs) There is no date/time handling in the SNMP MIBs other than what is provided in the Windows NT 4.0 SNMP service.   Two-digit shortcut handling: Commercial Internet System 2.5 does not use 2-digit shortcuts. Common date usage errors: Site Server 3.0 Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.

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: Commercial Internet System	Version: 2.5	Category:Compliant*
Language: Korean	OS: Win NT	Release Date: 18 May 1999
Operational Range:	01 Jan 1900 - 31 Dec 2078
Prerequisites:	Windows NT 4.0 Service Pack 4 or greater, Site Server 3 Service Pack 2, Windows NT Option Pack, SQL Server 6.5 Service Pack 5
Product Dependencies:	Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 5, SQL Server 6.5 with Service Pack 5 or SQL Server 7.0, Site Server 3 with Service Pack 2, Commercial Internet System 2.0.
Clock Dependencies:	Uses the Operating System date/time routines
Last Updated:	21 Oct 1999
Product Details
Microsoft Commercial Internet System (MCIS) 2.5 How the product handles dates: Please read the Year 2000 disclosure statement for Commercial Internet System 2.0 carefully. This document covers only those features that are provided with MCIS 2.5 and does not cover any features or components of MCIS 2.0. MCIS Administration and Provisioning Services 2.5 (MAPS) There are only two functions for which MAPS does date handling: credit card expiration and transaction time-stamping MAPS transaction time-stamping leverages the Microsoft SQL Server 6.5 or 7.0 datetime data type. Please see the disclosure statement for SQL Server 6.5 and 7.0 for more information. HTML Mail Interface (HMI) The only date handling in HMI exists in the Collaboration Data Objects. This functionality supplies date information for the RFC 822 header. This RFC requires a 4-digit date and Collaboration Data Objects has no known issues with that standard. There is no other date handling in HMI. Personal Web Pages (PWP) There is no date/time handling in PWP beyond what exists in Internet Information Server 4.0. Internet Information Server 4.0has no known issues. Simple Network Management Protocol Management Information Bases (SNMP MIBs) There is no date/time handling in the SNMP MIBs other than what is provided in the Windows NT 4.0 SNMP service.   Two-digit shortcut handling: Commercial Internet System 2.5 does not use 2-digit shortcuts. Common date usage errors: Site Server 3.0 Commerce––This component of the product is essentially a Software Development Kit (SDK). Therefore, year 2000 issues that users encounter with other SDK-type products are possible with this product. This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use.

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: Cordless Phone	Version: 2.0	Category:Compliant
Language: English	OS: Non-specific	Release Date: 01 Nov 1998
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows 95, Windows 98, DirectX 5.0, Internet Explorer 4.01, Microsoft Speech, Task Scheduler
Clock Dependencies:	OS File/Date API’s, MFC CTime
Last Updated:	18 Oct 1999
Product Details
Operational Range for Data:  midnight, January 1, 1970, to January 18, 19:14:07, 2038    How the product handles dates: Input: Microsoft Call Manager does not allow date input. Storage: Phone call information, including date and duration, are stored in the call log. All the call log data resides in the file MSP_CLOG.DAT in the Microsoft Phone directory. The date/time is stored as a FILETIME, which is a 64-bit value indicating the number of 100-nanosecond intervals since January 1, 1601. Voice messages left in the Answering System are stored in the Outlook Express mail store. Computation:   The duration of messages left in the Answering System are computed and stored as a property of the message placed in the Outlook Express mail store. The duration of calls stored in the Call Log is computed as a DWORD value. When retrieving messages remotely via the Answering System the age of the message is computed as well as the day of the week the message was left. Notification of new messages requires the scheduled date/time of the notification to be computed using the user chosen interval. Compressing the Outlook Express mail store is a scheduled activity, which requires date calculations to determine the start time. Display:   Microsoft Call Manager utilizes the Regional Settings in Control Panel for date/time format display. The date of messages is read aloud by TTS (Text-to-Speech) synthesis when retrieving messages remotely. Transfer: Call log entries, which include the date, can be copied from the History window to the Windows Clipboard. Two-digit shortcut handling: Two digit-shortcut dates are not used in Microsoft Call Manager, except for display as indicated by the Regional Date/Time display format in the Control Panel. (Also see Common date usage errors below) Common date usage errors: Call log entries copied onto the Windows Clipboard are formatted as plain text (clipboard format CF_TEXT). The date/time portion of the call log entry will be formatted as prescribed by the Regional Settings for date/time format in the Control Panel. If the date is formatted using two-digit year then the paste target application must correctly deal with two digit-shortcut dates. To alter this behavior, change the system short date format to one which uses four digit year (i.e. mm/dd/yyyy). Testing guidelines and recommendations: In general, avoid testing in a production environment or with non-duplicated production files because one cannot predict side effects with other products.

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: Creative Writer	Version: 1.0	Category:Compliant
Language: English	OS: 16-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98
Clock Dependencies:	None
Last Updated:	07 Jul 1999
Product Details
Release Date: July 95 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 1.0	Category:Compliant
Language: English	OS: Mac	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98
Clock Dependencies:	None
Last Updated:	07 Jul 1999
Product Details
Release Date: July 95 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	07 Jul 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: French	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: Italian	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: Spanish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: Creative Writer	Version: 2.0	Category:Compliant
Language: Swedish	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	None
Product Dependencies:	Internet Explorer, Windows 95, Windows 98, Windows NT 4.0
Clock Dependencies:	None
Last Updated:	29 Oct 1999
Product Details
Release Date: Oct 96 How the product handles dates: User files are the only data saved and dates may not be read from or written to these files. There are dates associated with the creation and modification of user files but these are handled by the operating system only. Two-digit shortcut handling: Not Applicable. What issues are there?: Older versions of Internet Explorer included on the CD may not contain updates for year 2000 compliance. Recommendations to meet compliance: Install the latest version of Internet Explorer from http://www.microsoft.com/ie.

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: DAO	Version: 3.0	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.0	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.0	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.5	Category:Compliant
Language: Korean	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: German	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: Japanese	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DAO	Version: 3.6	Category:Compliant
Language: Korean	OS: 32-Bit Win	Release Date: N/A
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLE32, Windows NT4.0 ServicePack 3, Windows 95+Internet Explorer 3.02 or newer, Data Sources (Servers), Microsoft Jet Desktop Database engine, OLEAUT, Visual Basic for Applications, msvcrt.dll
Clock Dependencies:	none
Last Updated:	10 Nov 1998
Product Details
Operational Range for Data: Data Source Dependent   How the product handles dates: DAO is not a storage engine and only deals with date conversion when handling variants. Date conversion is handled through OLE’s VariantChangeType(). Two-digit shortcut handling: OLE Automation or the Visual Basic for Applications/Visual Basic expression service is used to convert strings to date format. Common date usage errors: It is recommended to use 4-digit years when storing data or calling methods/properties of DAO. Using 2-digit years may reveal year-windowing issues in your backend, where the boundary cases may not be well known (given an arbitrary backend data store). Testing guidelines and recommendations: Since there is some "windowing" inherent in the Year 2000 compliance features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.

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: DCOM	Version: 9x	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 27 Nov 1997
Operational Range:	-
Prerequisites:	none
Product Dependencies:	OLEAUT32, Storage and Class Store, RPC RD4 Runtime, COM+ Admin,Base Windows NT v3.5 or later; Windows 9x
Clock Dependencies:	Uses GetTickCount ( ) API; internal timing only
Last Updated:	08 Nov 1999
Product Details
Operational Range for Data: Present day through 31 DEC 2036 How the product handles dates: The product obtains dates from the operating system via standard Windows APIs. The product also uses DOSDateTime ( ) for date calculations. Two-digit shortcut handling: The product does not allow users to enter dates. Hence, the product does not handle two-digit shortcuts. C Runtime information: The product uses two files (ctime.h & MKTime) which have known issues beyond 2035. Ctime.h miscalculates a leap year for AD 2038. This is a C runtime function. MKTime ( ) - there is a storage overflow problem in the year 2036. The API works by counting the seconds since Jan 1, 1970. Enough real-time seconds will have elapsed by the year 2036 that it will overflow the space allocated to keep track of the number used to store that value. Common date usage errors: Users do not enter dates, so no date usage errors exist.   Testing methodology: Microsoft conducted COM and DCOM specific testing using the dates in question. In addition, a hypothetical three-tiered application was created with Microsoft Transaction Server and COM/DCOM installed. Dates were inserted that were logical to test for in a SQL Server data store. At the conclusion of this test we did not observe either COM nor DCOM alter the dates, from beginning to end of transaction, whenever time and date data was accessed. Thus, no problems or changes in the dates were found.

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: DCOM95	Version: 1718	Category:Compliant
Language: English	OS: Win 95	Release Date: 01 Oct 1997
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Windows 95
Clock Dependencies:	GetTickCount, DosDateTimeToFileTime, FileTimeToDosDateTime,
Last Updated:	20 Oct 1998
Product Details
Description of how the product handles dates: All dates are stored internally as Win32 FILETIME structures. The FILETIME structure is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601. 2-digit shortcut handling: n/a (No user entry of dates occurs.) Common date usage errors: DCOM95 makes no use of dates. However, applications may be built on top of DCOM95 which use dates at the application level. These applications may have potential Year 2000 issues, and their Year 2000 status should be verified separately. Testing guidelines and recommendations: n/a

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: Digital Sound System 80	Version:	Category:Compliant
Language: English	OS: 32-Bit Win	Release Date: 01 Jun 1998
Operational Range:	01 Jan 1990 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	Win 9X
Clock Dependencies:	System Clock
Last Updated:	12 Nov 1999
Product Details
How the product handles dates: This product does not handle dates.

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: DirectX	Version: 7.0	Category:Compliant
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: 13 Sep 1999
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	Windows 95 with IE 3.02A Update, Windows 95 OSR2 + Windows 95 Y2K Update Win 95 OSR2.5 - IE 4 + Windows 95 Y2K Update Windows 98Windows 98 Second Edition
Clock Dependencies:	System clock
Last Updated:	24 Sep 1999
Product Details
How the product handles dates: DirectX 7.0 in general does not use or manipulate dates internally. The few minor exceptions are listed below: DirectInput uses the system date when creating a unique identifier for a newly installed DirectInput device (e.g. a joystick or gamepad). The Product Support tool DXDiag.exe displays the current date to the user. DirectMusic Producer displays the file creation date when you view the properties of a file within a project. Two-digit shortcut handling: DirectX 7.0 does not take date input from the user, so does not have issues with two-digit shortcut handling.   Testing guidelines and recommendations: Run all DirectX sample programs on year 2000 dates, and during the rollover from 12/31/99 to 1/1/2000 and 2/28/2000 to 2/29/2000. Install a joystick on 1/1/2000 and 2/29/2000 and verify the joystick works in a joystick-enabled application (or test in the Game Controllers Control Panel applet). Install a joystick before 1/1/2000 and verify it still works on 1/1/2000. Repeat for 2/29/2000. Engage in network play with a DirectPlay game where one client is in a time zone before the rollover boundary between 12/31/99 and one client is in a time zone after 1/1/2000 – repeat for the rollover from 2/28/2000 to 2/29/2000. Run DXDiag.exe and verify the correct date is displayed on important year 2000 dates. Run DirectMusic Producer on year 2000 dates and verify file load and save works correctly. Verify correct date is displayed for properties of project files.

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: DirectX	Version: 7.0	Category:Compliant
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: 13 Sep 1999
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	Windows 95 with IE 3.02A Update, Windows 95 OSR2 + Windows 95 Y2K Update Win 95 OSR2.5 - IE 4 + Windows 95 Y2K Update Windows 98Windows 98 Second Edition
Clock Dependencies:	System clock
Last Updated:	24 Sep 1999
Product Details
How the product handles dates: DirectX 7.0 in general does not use or manipulate dates internally. The few minor exceptions are listed below: DirectInput uses the system date when creating a unique identifier for a newly installed DirectInput device (e.g. a joystick or gamepad). The Product Support tool DXDiag.exe displays the current date to the user. DirectMusic Producer displays the file creation date when you view the properties of a file within a project. Two-digit shortcut handling: DirectX 7.0 does not take date input from the user, so does not have issues with two-digit shortcut handling.   Testing guidelines and recommendations: Run all DirectX sample programs on year 2000 dates, and during the rollover from 12/31/99 to 1/1/2000 and 2/28/2000 to 2/29/2000. Install a joystick on 1/1/2000 and 2/29/2000 and verify the joystick works in a joystick-enabled application (or test in the Game Controllers Control Panel applet). Install a joystick before 1/1/2000 and verify it still works on 1/1/2000. Repeat for 2/29/2000. Engage in network play with a DirectPlay game where one client is in a time zone before the rollover boundary between 12/31/99 and one client is in a time zone after 1/1/2000 – repeat for the rollover from 2/28/2000 to 2/29/2000. Run DXDiag.exe and verify the correct date is displayed on important year 2000 dates. Run DirectMusic Producer on year 2000 dates and verify file load and save works correctly. Verify correct date is displayed for properties of project files.

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: DirectX	Version: 7.0	Category:Compliant
Language: Czech	OS: 32-Bit Win	Release Date: 13 Sep 1999
Operational Range:	01 Jan 1980 - 31 Dec 2035
Prerequisites:	NONE
Product Dependencies:	Windows 95 with IE 3.02A Update, Windows 95 OSR2 + Windows 95 Y2K Update Win 95 OSR2.5 - IE 4 + Windows 95 Y2K Update Windows 98Windows 98 Second Edition
Clock Dependencies:	System clock
Last Updated:	24 Sep 1999
Product Details
How the product handles dates: DirectX 7.0 in general does not use or manipulate dates internally. The few minor exceptions are listed below: DirectInput uses the system date when creating a unique identifier for a newly installed DirectInput device (e.g. a joystick or gamepad). The Product Support tool DXDiag.exe displays the current date to the user. DirectMusic Producer displays the file creation date when you view the properties of a file within a project. Two-digit shortcut handling: DirectX 7.0 does not take date input from the user, so does not have issues with two-digit shortcut handling.   Testing guidelines and recommendations: Run all DirectX sample programs on year 2000 dates, and during the rollover from 12/31/99 to 1/1/2000 and 2/28/2000 to 2/29/2000. Install a joystick on 1/1/2000 and 2/29/2000 and verify the joystick works in a joystick-enabled application (or test in the Game Controllers Control Panel applet). Install a joystick before 1/1/2000 and verify it still works on 1/1/2000. Repeat for 2/29/2000. Engage in network play with a DirectPlay game where one client is in a time zone before the rollover boundary between 12/31/99 and one client is in a time zone after 1/1/2000 – repeat for the rollover from 2/28/2000 to 2/29/2000. Run DXDiag.exe and verify the correct date is displayed on important year 2000 dates. Run DirectMusic Producer on year 2000 dates and verify file load and save works correctly. Verify correct date is displayed for properties of project files.

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.