- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
07 Jul 1999 | ||
How the product handles dates: No internal code that depends on dates. Setup does version checking on files so it is not dependent on dates. Software works with following hardware:
|
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
07 Jul 1999 | ||
How the product handles dates: No internal code that depends on dates. Setup does version checking on files so it is not dependent on dates. Software works with following hardware:
|
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
07 Jul 1999 | ||
How the product handles dates: No internal code that depends on dates. Setup does version checking on files so it is not dependent on dates. Software works with following hardware:
|
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
07 Jul 1999 | ||
How the product handles dates: No internal code that depends on dates. Setup does version checking on files so it is not dependent on dates. Software works with following hardware:
|
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
- | ||
None | ||
Windows 95, Windows 98, all OEM Service Releases, DirectX Updates | ||
System Clock Ticker ( Not dependant on actual time, just clock ticks) | ||
08 Oct 1999 | ||
Release Date: 07/98 - 08/98 How the product handles dates: No internal code that
depends on dates. Setup does version checking on files so it is not dependent
on dates. Software works with following hardware: ·
SideWinder 3D PRO ·
SideWinder Game Pad ·
SideWinder Precision
Pro ·
SideWinder Force
Feedback Pro ·
SideWinder Freestyle
Pro ·
SideWinder Force
Feedback Wheel ·
SideWinder Dual
Strike Win 9x 1.00 ·
SideWinder Game Pad
Pro Win 9x Non-Specific ·
SideWinder Precision
Racing Wheel Win 9x 1.00 ·
SideWinder Dual Strike 1.0 Win9x USB Port ·
SideWinder Gamepad Pro Win9x USB Port · SideWinder Precision Racing Wheel 1.0 W9x USB Port |
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. |
01 Jan 1900 - 31 Dec 2078 | ||
Site Server 3.0 Service Pack 1 or greater | ||
Windows NT 4.0 with Service Pack 4, Windows NT 4.0 Option Pack (IIS4.0), Internet Explorer 4.01+, SQL 6.5 with Service Pack 4 or other ODBC 3.5 compliant databases | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Site Server 3.0 Commerce Server 3.0 Ad System 3.0 A version of Microsoft Wallet (client payment software) shipped with the Site Server 3.0, Commerce Edition sample sites that has a known Year 2000 issue. This issue is addressed in a corrected version of Microsoft Wallet that is available as part of Site Server 3.0 Service Pack 1 (and all subsequent Service Packs). The latest Site Server 3.0 Service Pack can be downloaded from http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.NOTE: this is an issue only for English versions of Site Server 3.0, Commerce Edition. Localized versions (French, German, Japanese, and Spanish) have the corrected version of Microsoft Wallet. The rest of Site Server 3.0, Commerce Edition has been tested and found to be compliant with Year 2000 guidelines. Description of how the product handles dates: See Product Guide for Site Server 3.0. The product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are all converted for display and storage in 4-digit years. 2-digit shortcut handling: See Product Guide for Site Server 3.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. All of the Commerce Sample Sites use a drop-down of dates for selection. The range extends past the year 2000 for sample purposes. 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––All Server code uses 4-digit year dates only. The Ad Manger 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 Product Guide for Site Server 3.0. Commerce–– This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. It is up to the store developer to insure that they follow the samples in order to avoid introducing any year 2000 issues. Ad System––Although not a Software Development Kit, 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. See comments for Internet Explorer 4 regarding optional use of the Wallet for entry of credit card expiration dates beyond the year 2000. Testing guidelines and recommendations: See Product Guide for Site Server 3.0. 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 of ActiveX Server Objects they author are Year 2000 compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To correct this, change the HTML. |
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. |
01 Jan 1900- - 31 Dec 2078 | ||
NONE | ||
Windows NT 4.0 with Service Pack 4, Windows NT 4.0 Option Pack (IIS4.0), Internet Explorer 4.01+, SQL 6.5 with Service Pack 4 or other ODBC 3.5 compliant databases | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Site Server 3.0 Commerce Edition consists of: Site Server 3.0 Commerce Server 3.0 Ad System 3.0 Description of how the product handles dates: See Product Guide for Site Server 3.0. The product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are all converted for display and storage in 4-digit years. 2-digit shortcut handling: See Product Guide for Site Server 3.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. All of the Commerce Sample Sites use a drop-down of dates for selection. The range extends past the year 2000 for sample purposes. 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––All Server code uses 4-digit year dates only. The Ad Manger 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 Product Guide for Site Server 3.0. Commerce–– This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. It is up to the store developer to insure that they follow the samples in order to avoid introducing any year 2000 issues. Ad System––Although not a Software Development Kit, 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. See comments for Internet Explorer 4 regarding optional use of the Wallet for entry of credit card expiration dates beyond the year 2000. Testing guidelines and recommendations: See Product Guide for Site Server 3.0. 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 of ActiveX Server Objects they author are Year 2000 compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To correct this, change the HTML. |
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. |
01 Jan 1900- - 31 Dec 2078 | ||
NONE | ||
Windows NT 4.0 with Service Pack 4, Windows NT 4.0 Option Pack (IIS4.0), Internet Explorer 4.01+, SQL 6.5 with Service Pack 4 or other ODBC 3.5 compliant databases | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Site Server 3.0 Commerce Edition consists of: Site Server 3.0 Commerce Server 3.0 Ad System 3.0 Description of how the product handles dates: See Product Guide for Site Server 3.0. The product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are all converted for display and storage in 4-digit years. 2-digit shortcut handling: See Product Guide for Site Server 3.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. All of the Commerce Sample Sites use a drop-down of dates for selection. The range extends past the year 2000 for sample purposes. 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––All Server code uses 4-digit year dates only. The Ad Manger 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 Product Guide for Site Server 3.0. Commerce–– This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. It is up to the store developer to insure that they follow the samples in order to avoid introducing any year 2000 issues. Ad System––Although not a Software Development Kit, 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. See comments for Internet Explorer 4 regarding optional use of the Wallet for entry of credit card expiration dates beyond the year 2000. Testing guidelines and recommendations: See Product Guide for Site Server 3.0. 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 of ActiveX Server Objects they author are Year 2000 compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To correct this, change the HTML. |
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. |
01 Jan 1900 - 31 Dec 2078 | ||
NONE | ||
Windows NT 4.0 with Service Pack 4, Windows NT 4.0 Option Pack (IIS4.0), Internet Explorer 4.01+, SQL 6.5 with Service Pack 4 or other ODBC | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Site Server 3.0 Commerce Edition consists of: Site Server 3.0 Commerce Server 3.0 Ad System 3.0 Description of how the product handles dates: See Product Guide for Site Server 3.0. The product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are all converted for display and storage in 4-digit years. 2-digit shortcut handling: See Product Guide for Site Server 3.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. All of the Commerce Sample Sites use a drop-down of dates for selection. The range extends past the year 2000 for sample purposes. 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––All Server code uses 4-digit year dates only. The Ad Manger 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 Product Guide for Site Server 3.0. Commerce–– This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. It is up to the store developer to insure that they follow the samples in order to avoid introducing any year 2000 issues. Ad System––Although not a Software Development Kit, 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. See comments for Internet Explorer 4 regarding optional use of the Wallet for entry of credit card expiration dates beyond the year 2000. Testing guidelines and recommendations: See Product Guide for Site Server 3.0. 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 of ActiveX Server Objects they author are Year 2000 compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To correct this, change the HTML. |
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. |
01 Jan 190 - 31 Dec 2078 | ||
NONE | ||
Windows NT 4.0 with Service Pack 4, Windows NT 4.0 Option Pack (IIS4.0), Internet Explorer 4.01+, SQL 6.5 with Service Pack 4 or other ODBC 3.5 compliant databases | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Site Server 3.0 Commerce Edition consists of: Site Server 3.0 Commerce Server 3.0 Ad System 3.0 Description of how the product handles dates: See Product Guide for Site Server 3.0. The product uses Windows and OLE API and SQL/ADO API to convert entered dates to the display/storage formats. Dates are all converted for display and storage in 4-digit years. 2-digit shortcut handling: See Product Guide for Site Server 3.0. Data entry is available only through a web page, and the product immediately uses the above-mentioned conversions on those entries. All of the Commerce Sample Sites use a drop-down of dates for selection. The range extends past the year 2000 for sample purposes. 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––All Server code uses 4-digit year dates only. The Ad Manger 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 Product Guide for Site Server 3.0. Commerce–– This product shows examples of using its formatting objects to get the right dates etc., but it doesn't enforce their use. It is up to the store developer to insure that they follow the samples in order to avoid introducing any year 2000 issues. Ad System––Although not a Software Development Kit, 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. See comments for Internet Explorer 4 regarding optional use of the Wallet for entry of credit card expiration dates beyond the year 2000. Testing guidelines and recommendations: See Product Guide for Site Server 3.0. 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 of ActiveX Server Objects they author are Year 2000 compliant. There are places in the sample sites that have date drop-downs that will expire in 3–5 years. To correct this, change the HTML. |
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. |
- | ||
NONE | ||
Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst) | ||
NONE | ||
27 Sep 1999 | ||
Description of how the product handles dates: Content Replication System: Compliant. Personalization: Not compliant. Uses 2-digit years in creating cookie expiration dates. Posting Acceptor: Compliant. Site Analyst: Not compliant. Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: Not compliant. Though UA maintains years as 4-digits internally and its operational range is 01/01/1971 - 12/31/2029, it is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. Web Publishing Wizard: Will not be tested for compliance. 2-digit shortcut handling: Personalization: uses 2-digit years. No logic for conversion. Site Analyst: 1/1/00 through 1/18/38 are interpreted as 1/1/2000 through 1/18/2038. 1/1/70 through 12/31/99 are interpreted as 1/1/1970 through 12/31/1999. Usage Analyst: There are several places/windows that allow users to enter years as two digits. In addition, many web log formats (like the IIS and CLF family of log formats) also record years in two digits. UA2 is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. None of the requests from log files that have dates on or after the year 2000 will be imported. How is the product not compliant?: Personalization: Expiration date stored in cookies uses only 2-digit year. There is no logic for converting 2-digit years to 4-digit years after the year 2000. Site Analyst: Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: None of the requests from log files that have dates on or after the year 2000 will be imported. Recommendations to meet compliance: Upgrade to Site Server 3.0. Apply Site Server 3.0 Service Pack 1. Please contact 1-888-MSFT-Y2K (or your local Microsoft Y2K Information line) and provide your Site Server license number to request an upgrade. Common date usage errors: Site Analyst: The failure to import date values disables the ability to search for web content based on modification date. |
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. |
- | ||
NONE | ||
Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst) | ||
NONE | ||
21 Sep 1999 | ||
Content Replication System: Compliant. Personalization: Not compliant. Uses 2-digit years in creating cookie expiration dates. Posting Acceptor: Compliant. Site Analyst: Not compliant. Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: Not compliant. Though UA maintains years as 4-digits internally and its operational range is 01/01/1971 - 12/31/2029, it is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. Web Publishing Wizard: Will not be tested for compliance. 2-digit shortcut handling: Personalization: uses 2-digit years. No logic for conversion. Site Analyst: 1/1/00 through 1/18/38 are interpreted as 1/1/2000 through 1/18/2038. 1/1/70 through 12/31/99 are interpreted as 1/1/1970 through 12/31/1999. Usage Analyst: There are several places/windows that allow users to enter years as two digits. In addition, many web log formats (like the IIS and CLF family of log formats) also record years in two digits. UA2 is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. None of the requests from log files that have dates on or after the year 2000 will be imported. How is the product not compliant?: Personalization: Expiration date stored in cookies uses only 2-digit year. There is no logic for converting 2-digit years to 4-digit years after the year 2000. Site Analyst: Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: None of the requests from log files that have dates on or after the year 2000 will be imported. Recommendations to meet compliance: Upgrade to Site Server 3.0. Apply Site Server 3.0 Service Pack 1. Please contact 1-888-MSFT-Y2K (or your local Microsoft Y2K Information line) and provide your Site Server license number to request an upgrade. Common date usage errors: Site Analyst: The failure to import date values disables the ability to search for web content based on modification date. |
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. |
- | ||
NONE | ||
Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst) | ||
NONE | ||
21 Sep 1999 | ||
Content Replication System: Compliant. Personalization: Not compliant. Uses 2-digit years in creating cookie expiration dates. Posting Acceptor: Compliant. Site Analyst: Not compliant. Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: Not compliant. Though UA maintains years as 4-digits internally and its operational range is 01/01/1971 - 12/31/2029, it is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. Web Publishing Wizard: Will not be tested for compliance. 2-digit shortcut handling: Personalization: uses 2-digit years. No logic for conversion. Site Analyst: 1/1/00 through 1/18/38 are interpreted as 1/1/2000 through 1/18/2038. 1/1/70 through 12/31/99 are interpreted as 1/1/1970 through 12/31/1999. Usage Analyst: There are several places/windows that allow users to enter years as two digits. In addition, many web log formats (like the IIS and CLF family of log formats) also record years in two digits. UA2 is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. None of the requests from log files that have dates on or after the year 2000 will be imported. How is the product not compliant?: Personalization: Expiration date stored in cookies uses only 2-digit year. There is no logic for converting 2-digit years to 4-digit years after the year 2000. Site Analyst: Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: None of the requests from log files that have dates on or after the year 2000 will be imported. Recommendations to meet compliance: Upgrade to Site Server 3.0. Apply Site Server 3.0 Service Pack 1. Please contact 1-888-MSFT-Y2K (or your local Microsoft Y2K Information line) and provide your Site Server license number to request an upgrade. Common date usage errors: Site Analyst: The failure to import date values disables the ability to search for web content based on modification date. |
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. |
- | ||
NONE | ||
Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst) | ||
NONE | ||
21 Sep 1999 | ||
Content Replication System: Compliant. Personalization: Not compliant. Uses 2-digit years in creating cookie expiration dates. Posting Acceptor: Compliant. Site Analyst: Not compliant. Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: Not compliant. Though UA maintains years as 4-digits internally and its operational range is 01/01/1971 - 12/31/2029, it is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. Web Publishing Wizard: Will not be tested for compliance. 2-digit shortcut handling: Personalization: uses 2-digit years. No logic for conversion. Site Analyst: 1/1/00 through 1/18/38 are interpreted as 1/1/2000 through 1/18/2038. 1/1/70 through 12/31/99 are interpreted as 1/1/1970 through 12/31/1999. Usage Analyst: There are several places/windows that allow users to enter years as two digits. In addition, many web log formats (like the IIS and CLF family of log formats) also record years in two digits. UA2 is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates. None of the requests from log files that have dates on or after the year 2000 will be imported. How is the product not compliant?: Personalization: Expiration date stored in cookies uses only 2-digit year. There is no logic for converting 2-digit years to 4-digit years after the year 2000. Site Analyst: Date values for web site content with year 2000 or greater will not be imported. Usage Analyst: None of the requests from log files that have dates on or after the year 2000 will be imported. Recommendations to meet compliance: Upgrade to Site Server 3.0. Apply Site Server 3.0 Service Pack 1. Please contact 1-888-MSFT-Y2K (or your local Microsoft Y2K Information line) and provide your Site Server license number to request an upgrade. Common date usage errors: Site Analyst: The failure to import date values disables the ability to search for web content based on modification date. |
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. |
01 Jan 1900 - 31 Dec 2078 | ||
Site Server Service Pack 2 | ||
Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0 | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Site Server 3.0 Service Pack 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Prerequisites: Site Server 3.0 Service Pack 2 is necessary for compliance. Service Pack 2 addresses known Year 2000 issues and has the additional features of making Site Server 3.0 and Site Server 3.0 Commerce Edition compatible with the Microsoft BackOffice® 4.5 platform, including support for SQL Server 7.0. Service Pack 2 is available at http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.How the product handles dates: Two-digit shortcut handling:
Testing guidelines and recommendations: 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 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 Site Server 3.
Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary. |
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. |
01 Jan 1900 - 31 Dec 2078 | ||
Site Server 3 Service Pack 2 | ||
Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0 | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Prerequisites Site Server 3.0 Service Pack 2 is necessary for compliance. Service Pack 2 addresses known Year 2000 issues and has the additional features of making Site Server 3.0 and Site Server 3.0 Commerce Edition compatible with the Microsoft BackOffice® 4.5 platform, including support for SQL Server 7.0. Service Pack 2 is available at http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.How the product handles dates:
Two-digit shortcut handling:
Testing guidelines and recommendations: 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 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 Site Server 3.
Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary. |
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. |
01 Jan 1900- - 31 Dec 2078 | ||
Site Server 3 Service Pack 2 | ||
Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0 | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Prerequisites Site Server 3.0 Service Pack 2 is necessary for compliance. Service Pack 2 addresses known Year 2000 issues and has the additional features of making Site Server 3.0 and Site Server 3.0 Commerce Edition compatible with the Microsoft BackOffice® 4.5 platform, including support for SQL Server 7.0. Service Pack 2 is available at http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.How the product handles dates:
Two-digit shortcut handling:
Testing guidelines and recommendations: 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 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 Site Server 3.
Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary. |
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. |
01 Jan 1900 - 31 Dec 2078 | ||
Site Server 3 Service Pack 2 | ||
Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0 | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Prerequisites Site Server 3.0 Service Pack 2 is necessary for compliance. Service Pack 2 addresses known Year 2000 issues and has the additional features of making Site Server 3.0 and Site Server 3.0 Commerce Edition compatible with the Microsoft BackOffice® 4.5 platform, including support for SQL Server 7.0. Service Pack 2 is available at http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.How the product handles dates:
Two-digit shortcut handling:
Testing guidelines and recommendations: 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 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 Site Server 3.
Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary. |
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. |
01 Jan 1900- - 31 Dec 2078 | ||
Site Server 3 Service Pack 2 | ||
Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0 | ||
Uses the operating system date/time routines | ||
21 Sep 1999 | ||
Prerequisites Site Server 3.0 Service Pack 2 is necessary for compliance. Service Pack 2 addresses known Year 2000 issues and has the additional features of making Site Server 3.0 and Site Server 3.0 Commerce Edition compatible with the Microsoft BackOffice® 4.5 platform, including support for SQL Server 7.0. Service Pack 2 is available at http://support.microsoft.com/support/siteserver/servicepacks/sp.asp.How the product handles dates:
Two-digit shortcut handling:
Testing guidelines and recommendations: 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 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 Site Server 3.
Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary. |
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. |
01 Jan 1980 - 31 Dec 2038 | ||
None | ||
Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 Recommended), Microsoft Internet Information Server 3.0 | ||
27 Sep 1999 | ||
The Site Server Enterprise Edition 2.0 product is comprised of two main programs - Site Server 2.0 and Commerce Server 2.0. The overall product is Not Compliant due primarily to issues in the Site Server 2.0 code. See the Site Server 2.0 compliance document for specific details. While Site Server 2.0 and Site Server Commerce are bundled and shipped together, they can be run independently of one another. If Site Server Commerce 2.0 is run with the Wallet upgrade (provided below), it will reach a rating of Compliant. What follows are known issues/workarounds with the Commerce Server portion of Site Server Enterprise Edition 2.0. How the product handles dates: Dates are passed and stored in a 4-digit manner. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. Two-digit shortcut handling: It is recommended that users use a 4-digit date when administering a store. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. What issues are known?: Please also see the Site Server 2.0 compliance document. Microsoft Wallet version 2.0 is included with this product. See the Product Guide for Internet Explorer version 4.0 for more information on Year 2000 issues and updates related to Microsoft Wallet. Additional information regarding upgrading Microsoft Wallet is below. Recommendations: Upgrade to Site Server Commerce Edition 3.0. Apply the latest Site Server 3.0 Service Pack, which is available at: <http://www.microsoft.com/siteserver/commerce>. Please contact 1-888-MSFT-Y2K (or your local Microsoft Year 2000 Information line) and provide your Site Server license number to request an upgrade.Upgrade all references to the Microsoft Wallet to point to version 2.01.00.1383. This will force a download of an updated, compliant version of the Microsoft Wallet. This is something that happens automatically with an ActiveX control. This control can also be obtained from http://www.microsoft.com/wallet/downloads/default.asp. Re-author administration pages that allow date entry, to require the use of a 4-digit year.
Common date usage errors: Since usage of this product does involve some development/authoring, the possibility of an author introducing a Year 2000 issue does exist. To minimize the possibilities of these issues, users should design for 4-digit year entries and pass 4-digit years to function calls that are made. Notes: Portions of Site Server Enterprise Edition 2.0 are implemented using the Python programming language. These libraries are known to work with dates up to, but not exceeding, the year 2038. |
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. |
01 Jan 1980 - 31 Dec 2038 | ||
None | ||
Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0 | ||
25 Mar 1999 | ||
The Site Server Enterprise Edition 2.0 product is comprised of two main programs - Site Server 2.0 and Commerce Server 2.0. The overall product is Not Compliant due primarily to issues in the Site Server 2.0 code. See the Site Server 2.0 compliance document for specific details. While Site Server 2.0 and Site Server Commerce are bundled and shipped together, they can be run independently of one another. If Site Server Commerce 2.0 is run with the Wallet upgrade (provided below), it will reach a rating of Compliant. What follows are known issues/workarounds with the Commerce Server portion of Site Server Enterprise Edition 2.0. How the product handles dates: Dates are passed and stored in a 4-digit manner. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. Two-digit shortcut handling: It is recommended that users use a 4-digit date when administering a store. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. What issues are known?: Please also see the Site Server 2.0 compliance document. Microsoft Wallet version 2.0 is included with this product. See the Product Guide for Internet Explorer version 4.0 for more information on Year 2000 issues and updates related to Microsoft Wallet. Additional information regarding upgrading Microsoft Wallet is below. Recommendations: Please also see the Site Server 2.0 Compliance Document. Upgrade all references to the Microsoft Wallet to point to version 2.01.00.1383. This will force a download of an updated, compliant version of the Microsoft Wallet. This is something that happens automatically with an ActiveX control. This control can also be obtained from http://www.microsoft.com/wallet/downloads/default.asp. Re-author administration pages that allow date entry, to require the use of a 4-digit year.
Common date usage errors: Since usage of this product does involve some development/authoring, the possibility of an author introducing a Year 2000 issue does exist. To minimize the possibilities of these issues, users should design for 4-digit year entries and pass 4-digit years to function calls that are made. Notes: Portions of Site Server Enterprise Edition 2.0 are implemented using the Python programming language. These libraries are known to work with dates up to, but not exceeding, the year 2038. |
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. |
01 Jan 1980 - 31 Dec 2038 | ||
None | ||
Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0 | ||
25 Mar 1999 | ||
The Site Server Enterprise Edition 2.0 product is comprised of two main programs - Site Server 2.0 and Commerce Server 2.0. The overall product is Not Compliant due primarily to issues in the Site Server 2.0 code. See the Site Server 2.0 compliance document for specific details. While Site Server 2.0 and Site Server Commerce are bundled and shipped together, they can be run independently of one another. If Site Server Commerce 2.0 is run with the Wallet upgrade (provided below), it will reach a rating of Compliant. What follows are known issues/workarounds with the Commerce Server portion of Site Server Enterprise Edition 2.0. How the product handles dates: Dates are passed and stored in a 4-digit manner. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. Two-digit shortcut handling: It is recommended that users use a 4-digit date when administering a store. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. What issues are known?: Please also see the Site Server 2.0 compliance document. Microsoft Wallet version 2.0 is included with this product. See the Product Guide for Internet Explorer version 4.0 for more information on Year 2000 issues and updates related to Microsoft Wallet. Additional information regarding upgrading Microsoft Wallet is below. Recommendations: Please also see the Site Server 2.0 Compliance Document. Upgrade all references to the Microsoft Wallet to point to version 2.01.00.1383. This will force a download of an updated, compliant version of the Microsoft Wallet. This is something that happens automatically with an ActiveX control. This control can also be obtained from http://www.microsoft.com/wallet/downloads/default.asp. Re-author administration pages that allow date entry, to require the use of a 4-digit year.
Common date usage errors: Since usage of this product does involve some development/authoring, the possibility of an author introducing a Year 2000 issue does exist. To minimize the possibilities of these issues, users should design for 4-digit year entries and pass 4-digit years to function calls that are made. Notes: Portions of Site Server Enterprise Edition 2.0 are implemented using the Python programming language. These libraries are known to work with dates up to, but not exceeding, the year 2038. |
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. |
01 Jan 1980 - 31 Dec 2038 | ||
None | ||
Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0 | ||
25 Mar 1999 | ||
The Site Server Enterprise Edition 2.0 product is comprised of two main programs - Site Server 2.0 and Commerce Server 2.0. The overall product is Not Compliant due primarily to issues in the Site Server 2.0 code. See the Site Server 2.0 compliance document for specific details. While Site Server 2.0 and Site Server Commerce are bundled and shipped together, they can be run independently of one another. If Site Server Commerce 2.0 is run with the Wallet upgrade (provided below), it will reach a rating of Compliant. What follows are known issues/workarounds with the Commerce Server portion of Site Server Enterprise Edition 2.0. How the product handles dates: Dates are passed and stored in a 4-digit manner. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. Two-digit shortcut handling: It is recommended that users use a 4-digit date when administering a store. In cases where a user enters a 2-digit date, the product uses the Visual Basic script libraries and the OLE data functions to convert these dates to a 4-digit value. What issues are known?: Please also see the Site Server 2.0 compliance document. Microsoft Wallet version 2.0 is included with this product. See the Product Guide for Internet Explorer version 4.0 for more information on Year 2000 issues and updates related to Microsoft Wallet. Additional information regarding upgrading Microsoft Wallet is below. Recommendations: Please also see the Site Server 2.0 Compliance Document. Upgrade all references to the Microsoft Wallet to point to version 2.01.00.1383. This will force a download of an updated, compliant version of the Microsoft Wallet. This is something that happens automatically with an ActiveX control. This control can also be obtained from http://www.microsoft.com/wallet/downloads/default.asp. Re-author administration pages that allow date entry, to require the use of a 4-digit year.
Common date usage errors: Since usage of this product does involve some development/authoring, the possibility of an author introducing a Year 2000 issue does exist. To minimize the possibilities of these issues, users should design for 4-digit year entries and pass 4-digit years to function calls that are made. Notes: Portions of Site Server Enterprise Edition 2.0 are implemented using the Python programming language. These libraries are known to work with dates up to, but not exceeding, the year 2038. |
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
23 Nov 1998 | ||
How the product handles dates: Two-digit shortcut handling: How is the product not compliant?: Recommendations to meet compliance: |
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
23 Nov 1998 | ||
How the product handles dates: Two-digit shortcut handling: How is the product not compliant?: Recommendations to meet compliance: |
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
23 Nov 1998 | ||
How the product handles dates: Two-digit shortcut handling: How is the product not compliant?: Recommendations to meet compliance: |
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. |
01 Jan 1971 - 31 Dec 2029 | ||
None | ||
Microsoft Access | ||
23 Nov 1998 | ||
How the product handles dates: Two-digit shortcut handling: |
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
none | ||
11 Nov 1998 | ||
How the product handles dates:
Two-digit shortcut handling:
|
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
none | ||
11 Nov 1998 | ||
How the product handles dates:
Two-digit shortcut handling:
|
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. |
01 Jan 1971 - 31 Dec 2029 | ||
none | ||
Microsoft Access | ||
none | ||
11 Nov 1998 | ||
How the product handles dates:
Two-digit shortcut handling:
|
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. |
01 Jan 1999 - 31 Dec 2035 | ||
None | ||
Macintosh running Netscape 3.x and higher or Internet Explorer 3.xx or higher; Windows 95/98/NT running Netscape 3.x and higher or Internet Explorer 3.xx or higher; Web TV | ||
None | ||
13 Aug 1999 | ||
Slate Magazine (www.slate.com)Release to Date: Released How the product handles dates: Slate stores time/date stamps for portions of the content in a SQL server database. SQL Server 7.0 has no known date handling issues. Check the SQL 7.0 product guide for further details. Two-digit shortcut handling: For 2-digit shortcuts Slate uses SQL Server to do the conversion. See SQL Server 7.0 compliance document for details.
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
none | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System clock | ||
18 Aug 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
- | ||
None | ||
Windows 95 or later, or Windows NT 4.0 or later | ||
System Clock | ||
01 Jul 1999 | ||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain Small Business Tools 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.Operational Range for Data: System dependent How the product handles dates: Dates and times that are displayed are obtained from the operating system. They are stored as 4-digit-year dates and displayed according to the user settings in the operating system. This product uses SYSTEMTIME structures, which do no form of truncation, and also uses OLE VARIANTs, which are Year 2000 compliant. Two-digit shortcut handling: The Properties dialog box (File menu) restores and displays file date information consistent with the long date format set in Regional Settings in the Windows Control Panel. Common date usage errors:
|
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. |
01 Jan 1970 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 2.11 Service Pack 2; SNA Server 2.11 Year 2000 software update | ||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 3.51 Service Pack 5 for Server | ||||||||||||||||||||||||||||||||||||||||||||||||||
See below | ||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
This covers the compliance of the SNA server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant. Clock Dependencies: System Clock, Prerequisites SNA Server 2.11 Service Pack 2 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.SNA Server 2.11 Year 2000 Software update is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.How the product handles dates: SNA Server 2.11 functions as an SNA protocol gateway. In addition, there are many services that provide functionality beyond protocol conversion that help integrate existing host applications and data with Windows applications and data. SNA Server does not manipulate dates in performing its protocol conversion, application integration, or data integration functions. Users of SNA Server do not enter dates All components provide diagnostic tracing which use time stamps. There are no known issues with these functions. The following table lists the additional functionality SNA Server provides, whether it uses dates in any form, how those dates are used and whether any issues exist for those functions.
Testing guidelines and recommendations: Operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be looked at carefully by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 2.11 Service Pack 2; SNA Server 2.11 Year 2000 Software Update | ||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 3.51 Service Pack 5 for Server, MS-DOS, Windows 3.x, Windows 9x, Windows NT for Clients | ||||||||||||||||||||||||||||||||||||||||||||||||||
see below | ||||||||||||||||||||||||||||||||||||||||||||||||||
25 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||
Clock Dependencies: System Clock,mktime( ) asctime( ) ctime( ) FileTimeToSystemTime( ) GetLocalTime( ) GetSystemTime( ) gmtime( ) localtime( ) mktime( ) SystemTimeToFileTime( ) time( ) Prerequisites SNA Server 2.11 Service Pack 2 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.SNA Server 2.11 Year 2000 Software update is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.How the product handles dates: SNA Server 2.11 functions as an SNA protocol gateway. In addition, there are many services that provide functionality beyond protocol conversion that help integrate existing host applications and data with Windows applications and data. SNA Server does not manipulate dates in performing its protocol conversion, application integration, or data integration functions. Users of SNA Server do not enter dates. SNA components provide diagnostic tracing which do use time stamps. There are no known issues with these functions. The following table lists the additional functionality SNA Server provides, whether it uses dates in any form, how those dates are used and whether issues exist for those functions.
Testing guidelines and recommendations: Operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server. As such they should be looked at carefully by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 3.0 Service Pack 3, NVALERT and AFTP software updates, or SNA Server 3.0 Service Pack 4.0 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
(see below) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This covers the compliance of the SNAS server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant. Clock Dependencies: System Clock,mktime( ) asctime( ) ctime( ) FileTimeToSystemTime( ) GetLocalTime( ) GetSystemTime( ) gmtime( ) localtime( ) mktime( ) SystemTimeToFileTime( ) time( ) Prerequisites SNA Server 3.0 Service Pack 3 and 4 are available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/. NVALERT and AFTP Software update available below. SNA Server 3.0 functions as an SNA protocol gateway. In addition, there are many services that provide functionality beyond protocol conversion that help integrate existing SNA applications and functions with Windows applications and functions. As an SNA protocol gateway, data is converted from Microsoft LAN protocols and SNA Server specific protocols to System Network Architecture (SNA) protocols. No dates are manipulated in this core functionality. No dates are entered by users. All components provide diagnostic tracing which use time stamps. There are no known issues with this function. The following table lists the additional functionality SNA Server provides, whether it uses dates in any form, how those dates are used and whether any issues exist for those functions.
Operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be looked at carefully by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 3.0 Service Pack 3, NVALERT and AFTP software updates, or SNA Server 3.0 Service Pack 4.0 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This covers the compliance of the SNAS server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Prerequisites SNA Server 3.0 Service Pack 3 or 4 are available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.
How the product handles dates: SNA Server 3.0 functions as an SNA protocol gateway. In addition, there are many services that provide functionality beyond protocol conversion that help integrate existing SNA applications and functions with Windows applications and functions. As an SNA protocol gateway, data is converted from Microsoft LAN protocols and SNA Server specific protocols to System Network Architecture (SNA) protocols. No dates are manipulated in this core functionality. No dates are entered by users. All components provide diagnostic tracing which use time stamps. There are no known issues with this function. The following table lists the additional functionality SNA Server provides, whether it uses dates in any form, how those dates are used and whether any issues exist for those functions.
Operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be looked at carefully by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 4.0 SP1; MDAC 2.0 Service Pack 2; upgrades for NValert, and AFTP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
25 Oct 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This covers the compliance of the SNA server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Prerequisites SNA Server 4.0 SP1 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/ Review the MS Data Access Components (MDAC) Product Guide document at http://www.microsoft.com/technet/year2k/product/user_view68559EN.htm. Software update for NVALERT and AFTP available below. Description of how dates are handled in the product: SNA Server 4.0 includes a core SNA protocol gateway and protocol conversion engine. In addition, several services provide additional capabilities including various forms of application and data integration. The following describes how dates are used for the product: No dates are entered by users. No dates are manipulated, changed, or generated in the core protocol gateway and conversion engine. All components provide diagnostic tracing which uses time stamps, and all of these time stamps are fully compliant. The following table lists components that make up the services and functions beyond the core protocol and gateway engine, how dates are used, and whether there are any known Year 2000 situations.
2 digit shortcuts: Not applicable, there is no user entry of dates. Common pitfalls for use or testing of SNA Server: None identified. Data transferred through SNA Server is unaffected. However, operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be reviewed by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 4.0 SP1; MDAC 2.0 Service Pack 2; software upgrade for NValert and AFTP | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This covers the compliance of the SNA server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Prerequisites SNA Server 4.0 Service Pack 1 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/. Review the MS Data Access Components (MDAC) Product Guide document at http://www.microsoft.com/technet/year2k/product/user_view68559EN.htm. Software update for NVALERT and AFTP available below. Description of how dates are handled in the product: SNA Server 4.0 includes a core SNA protocol gateway and protocol conversion engine. In addition, several services provide additional capabilities including various forms of application and data integration. The following describes how dates are used for the product: No dates are entered by users. No dates are manipulated, changed, or generated in the core protocol gateway and conversion engine. All components provide diagnostic tracing which uses time stamps, and all of these time stamps are fully compliant. The following table lists components that make up the services and functions beyond the core protocol and gateway engine, how dates are used, and whether there are any known Year 2000 situations.
2 digit shortcuts: Not applicable, there is no user entry of dates. Common pitfalls for use or testing of SNA Server: None identified. Data transferred through SNA Server is unaffected. However, operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be reviewed by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 4.0 Service Pack 2; MDAC 2.11.3711.11 or later | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{See below} | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain SNA Server 4.0 Service Pack 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.This covers the compliance of the SNAS server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Prerequisites SNA Server 4.0 Service Pack 2 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/ Review the MS Data Access Components (MDAC) Product Guide document at http://www.microsoft.com/technet/year2k/product/user_view68546EN.htm. Description of how dates are handled in the product: SNA Server 4.0 includes a core SNA protocol gateway and protocol conversion engine. In addition, several services provide additional capabilities including various forms of application and data integration. The following describes how dates are used for the product: No dates are entered by users. No dates are manipulated, changed, or generated in the core protocol gateway and conversion engine. All components provide diagnostic tracing which uses time stamps, and all of these time stamps are fully compliant. The following table lists components that make up the services and functions beyond the core protocol and gateway engine, how dates are used, and whether there are any known Y2K situations.
2 digit shortcuts: Not applicable, there is no user entry of dates. Common pitfalls for use or testing of SNA Server: None identified. Data transferred through SNA Server is unaffected. However, operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be reviewed by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNA Server 4.0 Service Pack 2; MDAC 2.11.3711.11 or later | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain SNA Server 4.0 Service Pack 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.This covers the compliance of the SNAS server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Description of how dates are handled in the product:
2 digit shortcuts: Not applicable, there is no user entry of dates. Common pitfalls for use or testing of SNA Server: None identified. Data transferred through SNA Server is unaffected. However, operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be reviewed by the user. |
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
MDAC 2.1.2.4202.3 (GA) or later. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock, mktime( ), asctime( ), ctime( ), FileTimeToSystemTime( ), GetLocalTime( ), GetSystemTime( ), gmtime( ), localtime( ), mktime( ), SystemTimeToFileTime( ), time( ) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
05 Oct 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers' Year 2000 efforts, Microsoft intends to maintain SNA Server 4.0 Service Pack 2 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.This covers the compliance of the SNAS server client components running on Windows NT, Windows 9.x, Windows 3.x, and DOS 6.22 to the extent the platforms are compliant.
Prerequisites SNA Server 4.0 Service Pack 3 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/ Review the MS Data Access Components (MDAC) Product Guide document at http://www.microsoft.com/technet/year2k/product/user_view68546EN.htm. How dates are handled in the product: SNA Server 4.0 includes a core SNA protocol gateway and protocol conversion engine. In addition, several services provide additional capabilities including various forms of application and data integration. The following describes how dates are used for the product: Dates are not entered by users. Dates are not manipulated, changed, or generated in the core protocol gateway and conversion engine. Components provide diagnostic tracing which uses time stamps, and these time stamps have no known issues. The following table lists components that make up the services and functions beyond the core protocol and gateway engine, how dates are used, and whether there are any known year 2000 issues.
Two-digit shortcut handlng: Not applicable, there is no user entry of dates. Common pitfalls for use or testing of SNA Server: None identified. Data transferred through SNA Server is unaffected. However, operating systems and applications on the SNA Host or client applications are provided by third parties and are beyond the scope of SNA Server and should be reviewed by the user.
|
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||||||||||||||||||||||||||
NVALERT software update | |||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT Workstation 4.0 Service Pack 4 | |||||||||||||||||||||||||||||||||||||||||||||||||||
{see below} | |||||||||||||||||||||||||||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||||||||||||||||||||||||||
SystemTimeToFileTime( )time( ) Prerequisites NVALERT available below. How the product handles dates: SNA Workstation 3.0 functions as an SNA protocol gateway. In addition, there are many services that provide functionality beyond protocol conversion that help integrate existing SNA applications and functions with Windows applications and functions. As an SNA protocol gateway, data is converted from Microsoft LAN protocols and SNA Server specific protocols to System Network Architecture (SNA) protocols. No dates are manipulated in this core functionality. No dates are entered by users. All components provide diagnostic tracing which uses time stamps. There are no known issues with this function. The following table lists the additional functionality SNA Workstation provides, whether it uses dates in any form, how those dates are used and whether any issues exist for those functions.
|
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. |
01 Jan 1970 - 31 Dec 2035 | |||||||||||||||||||||||||||
NVALERT Software Update | |||||||||||||||||||||||||||
Windows NT Workstation 4.0 Service Pack 4 | |||||||||||||||||||||||||||
{See below} | |||||||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||||||
SNA 4.0 Service Pack 1 is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/. NVALERT available below. Description of how dates are handled in the product. SNA Workstation 4.0 includes a SNA protocol gateway and protocol conversion engine. In addition, several services provide additional capabilities including various forms of application and data integration. The following describes how dates are used for the product: No dates are entered by users. No dates are manipulated, changed, or generated in the core protocol gateway and conversion engine. All components provide diagnostic tracing which uses time stamps, and all of these time stamps are fully compliant. The following table lists components that make up the services and functions beyond the core protocol and gateway engine, how dates are used, and whether there are any known Y2K situations.
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
SQL 6.0 Service Pack 3 | |||
Microsoft Data Access Components (MDAC), Server and Client platforms documented in SQL Server System requirements. | |||
System clock | |||
27 Oct 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements. | |||
System clock | |||
02 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements. | |||
System clock | |||
02 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
SQL 6.0 Service Pack 3 | |||
ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements. | |||
System clock | |||
02 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC) | |||
Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
27 Oct 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC) | |||
Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
27 Oct 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC) | |||
Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
27 Oct 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC) | |||
Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
27 Oct 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements. | |||
System clock | |||
11 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
11 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
11 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
11 Nov 1999 | |||
|
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. |
01 Jan 1753 - 31 Dec 9999 | |||
None | |||
Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements. | |||
System Clock | |||
11 Nov 1999 | |||
|
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. |
- | ||
NONE | ||
DOS or Win 3.1 | ||
System Clock | ||
02 Nov 1999 | ||
How the product handles dates: No date handling or two-digit shortcut interpretation is performed. |
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. |
01 Jan 1980 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Systems Management Server 1.2 Service Pack 4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. |
01 Jan 1980 - 31 Dec 2035 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Systems Management Server 1.2 Service Pack 4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. |
01 Jan 1980 - 31 Dec 2053 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Systems Management Server 1.2 Service Pack 4 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
System Clock | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
21 Oct 1999 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
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. |
ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA. ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.
|
||
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act. |