Microsoft TechNet ITHome - Microsoft Year 2000 Product Guide
Microsoft Products
Product Entry Guide Detail


The Microsoft Year 2000 Resource Center Product Guide details specific Year 2000 information concerning Microsoft products. The information in the product guide is presented to assist IT professionals in planning their transition to the Year 2000. If you cannot find a specific product and it is not on the "Microsoft Products: Testing Yet to be Completed" list, you can assume it will NOT be tested for compliancy.
Microsoft will continually update the Year 2000 Product Guide with the most current Year 2000 test information. Visit the Year 2000 Product Guide for more details regarding the Microsoft Compliance Categories.

------------------------
Microsoft Year 2000 Resource Center
SideWinder  2.0   (Japanese)

Product Summary
Product: SideWinder Version: 2.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 05 Aug 1997
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 07 Jul 1999
Product Details

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

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  2.0   (Korean)

Product Summary
Product: SideWinder Version: 2.0 Category:Compliant
Language: Korean OS: 32-Bit Win Release Date: 05 Aug 1997
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 07 Jul 1999
Product Details

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

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  2.0   (Portuguese)

Product Summary
Product: SideWinder Version: 2.0 Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: 05 Aug 1997
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 07 Jul 1999
Product Details

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

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  2.0   (Spanish)

Product Summary
Product: SideWinder Version: 2.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 05 Aug 1997
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 07 Jul 1999
Product Details

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

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (English)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (French)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (German)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (Italian)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (Japanese)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (Portuguese)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SideWinder  3.XX   (Spanish)

Product Summary
Product: SideWinder Version: 3.XX Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95, Windows 98, all OEM Service Releases, DirectX Updates
Clock Dependencies: System Clock Ticker ( Not dependant on actual time, just clock ticks)
Last Updated: 08 Oct 1999
Product Details

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

 

 

 

 

 

 

 

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server - Commerce  3.0   (English)

Product Summary
Product: Site Server - Commerce Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900 - 31 Dec 2078
Prerequisites: Site Server 3.0 Service Pack 1 or greater
Product Dependencies: 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
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details



Site Server 3.0 Commerce Edition consists of:
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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server - Commerce  3.0   (French)

Product Summary
Product: Site Server - Commerce Version: 3.0 Category:Compliant
Language: French OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900- - 31 Dec 2078
Prerequisites: NONE
Product Dependencies: 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
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details
   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.
             
 
 
 
 
 

Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server - Commerce  3.0   (German)

Product Summary
Product: Site Server - Commerce Version: 3.0 Category:Compliant
Language: German OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900- - 31 Dec 2078
Prerequisites: NONE
Product Dependencies: 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
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details
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.

Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server - Commerce  3.0   (Japanese)

Product Summary
Product: Site Server - Commerce Version: 3.0 Category:Compliant
Language: Japanese OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900 - 31 Dec 2078
Prerequisites: NONE
Product Dependencies: 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
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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.

Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server - Commerce  3.0   (Spanish)

Product Summary
Product: Site Server - Commerce Version: 3.0 Category:Compliant
Language: Spanish OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 190 - 31 Dec 2078
Prerequisites: NONE
Product Dependencies: 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
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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.

Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  2.0   (English)

Product Summary
Product: Site Server Version: 2.0 Category:Not Compliant
Language: English OS: Win NT Release Date: 19 May 1997
Operational Range: -
Prerequisites: NONE
Product Dependencies: Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst)
Clock Dependencies: NONE
Last Updated: 27 Sep 1999
Product Details

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  2.0   (French)

Product Summary
Product: Site Server Version: 2.0 Category:Not Compliant
Language: French OS: Win NT Release Date: 19 May 1997
Operational Range: -
Prerequisites: NONE
Product Dependencies: Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst)
Clock Dependencies: NONE
Last Updated: 21 Sep 1999
Product Details



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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  2.0   (German)

Product Summary
Product: Site Server Version: 2.0 Category:Not Compliant
Language: German OS: Win NT Release Date: 19 May 1997
Operational Range: -
Prerequisites: NONE
Product Dependencies: Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst)
Clock Dependencies: NONE
Last Updated: 21 Sep 1999
Product Details



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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  2.0   (Japanese)

Product Summary
Product: Site Server Version: 2.0 Category:Not Compliant
Language: Japanese OS: Win NT Release Date: 19 May 1997
Operational Range: -
Prerequisites: NONE
Product Dependencies: Windows NT Server 4.0 + Service Pack 2, Internet Information Server 3.0, SQL 6.5 (for Usage Analyst)
Clock Dependencies: NONE
Last Updated: 21 Sep 1999
Product Details



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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  3.0   (English)

Product Summary
Product: Site Server Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900 - 31 Dec 2078
Prerequisites: Site Server Service Pack 2
Product Dependencies: Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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:

  • For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900, and December 31, 2078.
  • For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753 to December 31, 9999.

Two-digit shortcut handling:

  • With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
  • The Web Admin gives a message if the user tries to enter a year with 2 digits.
  • In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
  • With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
  • Membership Directory Manager supports dates in 2-digit shortcuts.
  • With the Membership Directory Manager, the logic is the same as for Internet Explorer 4.0.

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.

  • Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
  • Also, start replication between servers just prior to midnight, December 31, 1999.
  • Add members to Membership Groups with expiration date set to right before and after January 1, 2000.

Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  3.0   (French)

Product Summary
Product: Site Server Version: 3.0 Category:Compliant*
Language: French OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900 - 31 Dec 2078
Prerequisites: Site Server 3 Service Pack 2
Product Dependencies: Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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:

  • For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900, and December 31, 2078.
  • For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753 to December 31, 9999.

Two-digit shortcut handling:

  • With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
  • The Web Admin gives a message if the user tries to enter a year with 2 digits.
  • In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
  • With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
  • Membership Directory Manager supports dates in 2-digit shortcuts.
  • With the Membership Directory Manager, the logic is the same as for Internet Explorer 4.0.

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.

  • Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
  • Also, start replication between servers just prior to midnight, December 31, 1999.
  • Add members to Membership Groups with expiration date set to right before and after January 1, 2000.

Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  3.0   (German)

Product Summary
Product: Site Server Version: 3.0 Category:Compliant*
Language: German OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900- - 31 Dec 2078
Prerequisites: Site Server 3 Service Pack 2
Product Dependencies: Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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:

  • For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900, and December 31, 2078.
  • For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753 to December 31, 9999.

Two-digit shortcut handling:

  • With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
  • The Web Admin gives a message if the user tries to enter a year with 2 digits.
  • In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
  • With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
  • Membership Directory Manager supports dates in 2-digit shortcuts.
  • With the Membership Directory Manager, the logic is the same as for Internet Explorer 4.0.

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.

  • Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
  • Also, start replication between servers just prior to midnight, December 31, 1999.
  • Add members to Membership Groups with expiration date set to right before and after January 1, 2000.

Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  3.0   (Japanese)

Product Summary
Product: Site Server Version: 3.0 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900 - 31 Dec 2078
Prerequisites: Site Server 3 Service Pack 2
Product Dependencies: Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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:

  • For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900, and December 31, 2078.
  • For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753 to December 31, 9999.

Two-digit shortcut handling:

  • With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
  • The Web Admin gives a message if the user tries to enter a year with 2 digits.
  • In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
  • With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
  • Membership Directory Manager supports dates in 2-digit shortcuts.
  • With the Membership Directory Manager, the logic is the same as for Internet Explorer 4.0.

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.

  • Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
  • Also, start replication between servers just prior to midnight, December 31, 1999.
  • Add members to Membership Groups with expiration date set to right before and after January 1, 2000.

Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server  3.0   (Spanish)

Product Summary
Product: Site Server Version: 3.0 Category:Compliant*
Language: Spanish OS: Win NT Release Date: 01 Jun 1998
Operational Range: 01 Jan 1900- - 31 Dec 2078
Prerequisites: Site Server 3 Service Pack 2
Product Dependencies: Windows NT4.0 with Service Pack 4, Windows NT 4.0 Option Pack (Internet Information Server 4.0), Internet Explorer 4.0
Clock Dependencies: Uses the operating system date/time routines
Last Updated: 21 Sep 1999
Product Details

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:

  • For Content Replication, date and time is stored as an 8-byte real value (double), with a positive number representing a date between January 1, 1900, and December 31, 2078.
  • For Personalization and Membership, the date and time is stored as an 8-byte field. Four bytes for the number of dates before or after the base date of January 1, 1900, and four bytes for the number of milliseconds after midnight. Dates range from January 1, 1753 to December 31, 9999.

Two-digit shortcut handling:

  • With the Microsoft Management Console, the input of dates is controlled by selecting from a drop-down box that displays dates in a 4-digit year format.
  • The Web Admin gives a message if the user tries to enter a year with 2 digits.
  • In the Rule Builder, 2-digit shortcuts are allowed when editing rules. The 2-digit shortcut is enabled if the system short date format is set for "yy".
  • With the Rule Builder, the conversion is done using various external objects, such as the OLE date time pickers, and components gained either from the operating system or Internet Explorer 4.
  • Membership Directory Manager supports dates in 2-digit shortcuts.
  • With the Membership Directory Manager, the logic is the same as for Internet Explorer 4.0.

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.

  • Post data between systems that have one set to December 31, 1999 and the other set to January 1, 2000, simulating time-zone issues.
  • Also, start replication between servers just prior to midnight, December 31, 1999.
  • Add members to Membership Groups with expiration date set to right before and after January 1, 2000.

Import Content Analyst log files that contain information that cross the 1999 to 2000 boundary.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Enterprise  2.0   (English)

Product Summary
Product: Site Server Enterprise Version: 2.0 Category:Not Compliant
Language: English OS: 32-Bit Win Release Date: 19 May 1997
Operational Range: 01 Jan 1980 - 31 Dec 2038
Prerequisites: None
Product Dependencies: Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 Recommended), Microsoft Internet Information Server 3.0
Clock Dependencies:
Last Updated: 27 Sep 1999
Product Details

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Enterprise  2.0   (French)

Product Summary
Product: Site Server Enterprise Version: 2.0 Category:Not Compliant
Language: French OS: 32-Bit Win Release Date: 19 May 1997
Operational Range: 01 Jan 1980 - 31 Dec 2038
Prerequisites: None
Product Dependencies: Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0
Clock Dependencies:
Last Updated: 25 Mar 1999
Product Details

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Enterprise  2.0   (German)

Product Summary
Product: Site Server Enterprise Version: 2.0 Category:Not Compliant
Language: German OS: 32-Bit Win Release Date: 19 May 1997
Operational Range: 01 Jan 1980 - 31 Dec 2038
Prerequisites: None
Product Dependencies: Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0
Clock Dependencies:
Last Updated: 25 Mar 1999
Product Details

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Enterprise  2.0   (Japanese)

Product Summary
Product: Site Server Enterprise Version: 2.0 Category:Not Compliant
Language: Japanese OS: 32-Bit Win Release Date: 19 May 1997
Operational Range: 01 Jan 1980 - 31 Dec 2038
Prerequisites: None
Product Dependencies: Microsoft Windows NT Server 4.0 + Windows NT Server Service Pack 2 or better (Service Pack 4 recommended), Microsoft Internet Information Server 3.0
Clock Dependencies:
Last Updated: 25 Mar 1999
Product Details

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  2.0   (English)

Product Summary
Product: Site Server Express Version: 2.0 Category:Not Compliant
Language: English OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies:
Last Updated: 23 Nov 1998
Product Details

How the product handles dates:
The "Analysis" applications in Site Server Express version 2.0 (SSX2) always maintains years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath). However, this product is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates.

Two-digit shortcut handling:
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. None of the requests from log files that only contain dates on or after the year 2000 may be imported. Site Server Express will import requests from log files that include dates on or after the year 2000 provided that there are also dates that precede the year 2000 in the same log file to begin with.

How is the product not compliant?:
SSX2 will not import requests from log files that include dates >= 1/1/2000 unless there are dates in the same log file that are <=1/1/2000.

Recommendations to meet compliance:
Upgrade to Site Server Express version 3.0.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  2.0   (German)

Product Summary
Product: Site Server Express Version: 2.0 Category:Not Compliant
Language: German OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies:
Last Updated: 23 Nov 1998
Product Details

How the product handles dates:
The "Analysis" applications in Site Server Express version 2.0 (SSX2) always maintains years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath). However, this product is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates.

Two-digit shortcut handling:
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. None of the requests from log files that only contain dates on or after the year 2000 may be imported. Site Server Express will import requests from log files that include dates on or after the year 2000 provided that there are also dates that precede the year 2000 in the same log file to begin with.

How is the product not compliant?:
SSX2 will not import requests from log files that include dates >= 1/1/2000 unless there are dates in the same log file that are <=1/1/2000.

Recommendations to meet compliance:
Upgrade to Site Server Express version 3.0.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  2.0   (Japanese)

Product Summary
Product: Site Server Express Version: 2.0 Category:Not Compliant
Language: Japanese OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies:
Last Updated: 23 Nov 1998
Product Details

How the product handles dates:
The "Analysis" applications in Site Server Express version 2.0 (SSX2) always maintains years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath). However, this product is known to have multiple problems when translating from two-digit year short cuts to four-digit year dates.

Two-digit shortcut handling:
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. None of the requests from log files that only contain dates on or after the year 2000 may be imported. Site Server Express will import requests from log files that include dates on or after the year 2000 provided that there are also dates that precede the year 2000 in the same log file to begin with.

How is the product not compliant?:
SSX2 will not import requests from log files that include dates >= 1/1/2000 unless there are dates in the same log file that are <=1/1/2000.

Recommendations to meet compliance:
Upgrade to Site Server Express version 3.0.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  3.0   (English)

Product Summary
Product: Site Server Express Version: 3.0 Category:Compliant
Language: English OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: None
Product Dependencies: Microsoft Access
Clock Dependencies:
Last Updated: 23 Nov 1998
Product Details

How the product handles dates:
The "Analysis" applications in Site Server Express version 3.0 (SSX3) always maintain years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath).

Two-digit shortcut handling:
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. In SSX3, we translate 71-99 into 1971-1999 and 00-29 into 2000-2029. Two-digit year shortcuts are always stored as four digit numbers internally.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  3.0   (French)

Product Summary
Product: Site Server Express Version: 3.0 Category:Compliant
Language: French OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies: none
Last Updated: 11 Nov 1998
Product Details

How the product handles dates:


The "Analysis" applications in Site Server Express version 3.0 (SSX3) always maintain years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath).

Two-digit shortcut handling:


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. In SSX3, we translate 71-99 into 1971-1999 and 00-29 into 2000-2029. Two-digit year shortcuts are always stored as four digit numbers internally


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  3.0   (German)

Product Summary
Product: Site Server Express Version: 3.0 Category:Compliant
Language: German OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies: none
Last Updated: 11 Nov 1998
Product Details

How the product handles dates:


The "Analysis" applications in Site Server Express version 3.0 (SSX3) always maintain years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath).

Two-digit shortcut handling:


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. In SSX3, we translate 71-99 into 1971-1999 and 00-29 into 2000-2029. Two-digit year shortcuts are always stored as four digit numbers internally


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Site Server Express  3.0   (Japanese)

Product Summary
Product: Site Server Express Version: 3.0 Category:Compliant
Language: Japanese OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1971 - 31 Dec 2029
Prerequisites: none
Product Dependencies: Microsoft Access
Clock Dependencies: none
Last Updated: 11 Nov 1998
Product Details

How the product handles dates:


The "Analysis" applications in Site Server Express version 3.0 (SSX3) always maintain years as 4-digits internally. Its operational range is 01/01/1971 - 12/31/2029 (The 2029 dependency is because of use of the Access database underneath).

Two-digit shortcut handling:


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. In SSX3, we translate 71-99 into 1971-1999 and 00-29 into 2000-2029. Two-digit year shortcuts are always stored as four digit numbers internally


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Slate Magazine    (English)

Product Summary
Product: Slate Magazine Version: Category:Compliant
Language: English OS: Non-specific Release Date: N/A
Operational Range: 01 Jan 1999 - 31 Dec 2035
Prerequisites: None
Product Dependencies: 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
Clock Dependencies: None
Last Updated: 13 Aug 1999
Product Details

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.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Arabic)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Arabic OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Chinese - Simplified)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Chinese - Traditional)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Croatian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Croatian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Czech)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Czech OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Danish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Danish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Dutch)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Dutch OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (English)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (English Australian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: English Australian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (English British)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: English British OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Estonian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Estonian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Finnish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Finnish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (French)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (German)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Greek)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Greek OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Hebrew)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Hebrew OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Hindu)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Hindu OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Hungarian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Hungarian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Italian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Japanese)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Korean)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Korean OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Latvian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Latvian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Lithuanian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Lithuanian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Norwegian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Norwegian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Pan-Chinese)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Pan-Chinese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Polish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Polish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Portuguese (Brazil))

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Portuguese)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Romanian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Romanian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Russian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Russian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Slovenian)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Slovenian OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Spanish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Swedish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Swedish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: none
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Thai)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Thai OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System clock
Last Updated: 18 Aug 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Small Business Tools 2000  9.0   (Turkish)

Product Summary
Product: Small Business Tools 2000 Version: 9.0 Category:Compliant
Language: Turkish OS: 32-Bit Win Release Date: 25 Mar 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows 95 or later, or Windows NT 4.0 or later
Clock Dependencies: System Clock
Last Updated: 01 Jul 1999
Product Details

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:

  • Using the short date input mask will limit the ability of users to enter dates outside of the 2-digit-year shortcut range (see "Two-digit shortcut handling," above).
  • Use Date/Time fields—not Text fields—in tables to store date data.
  • Use a 2-digit-year format to display dates: avoid using the short date format (mm/dd/yy). Use the long date format (mm/dd/yyyy), the short date format in conjunction with Regional Settings in Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
    Note: Planning for 4-digit-year display is important in programs where columns may be fixed by the author with widths that are too narrow for 4-digit years.
  • The text export method, including Visual Basic for Applications TransferText, should always be set for export of 4-digit years.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  2.11   (English)

Product Summary
Product: SNA Server Version: 2.11 Category:Compliant*
Language: English OS: Win NT Release Date: 28 Jun 1995
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 2.11 Service Pack 2; SNA Server 2.11 Year 2000 software update
Product Dependencies: Windows NT 3.51 Service Pack 5 for Server
Clock Dependencies: See below
Last Updated: 21 Sep 1999
Product Details

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,
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

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.

Component

Uses Dates

Use of Dates

Known Issues

Administration

Yes

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Yes

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Yes

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT was incorrectly setting the date field for year 2000 onward.

A software update for Intel and Alpha platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

AFTP (File Transfer)

Yes

Displays and sets modification and access times on files transferred between systems.

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file was created on 3/18/2001, the AFTP Server would display a date of 3/18/101.

A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

SNA Gateway

Yes

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Yes

Compares file timestamps between system and files to be installed.

None

RASSNA (RAS over a SNA network)

Yes

Logs timestamps in trace statements.

None

TN3270

Yes

Logs timestamps in trace statements.

None

Windows 95 Client

Yes

Logs timestamps in trace statements.

None

MS-DOS Client

Yes

Logs timestamps in trace statements.

None

Windows 3.x Client

Yes

Logs timestamps in trace statements.

None

 

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  2.11   (Japanese)

Product Summary
Product: SNA Server Version: 2.11 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 26 Jan 1996
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 2.11 Service Pack 2; SNA Server 2.11 Year 2000 Software Update
Product Dependencies: Windows NT 3.51 Service Pack 5 for Server, MS-DOS, Windows 3.x, Windows 9x, Windows NT for Clients
Clock Dependencies: see below
Last Updated: 25 Oct 1999
Product Details

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.

Component

Uses Dates

Use of Dates

Known Issues

Administration

Yes

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Yes

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Yes

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT was incorrectly setting the date field for year 2000 onward.

A software update for this issue is available HERE.

AFTP (File Transfer)

Yes

Displays and sets modification and access times on files transferred between systems.

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file were created on 3/18/2001, the AFTP Server would display a date of 3/18/101.

A software update for this issue is available HERE.

SNA Gateway

Yes

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Yes

Compares file timestamps between system and files to be installed.

None

RASSNA (RAS over a SNA network)

Yes

Logs timestamps in trace statements.

None

TN3270

Yes

Logs timestamps in trace statements.

None

Windows 95 Client

Yes

Logs timestamps in trace statements.

None

MS-DOS Client

Yes

Logs timestamps in trace statements.

None

Windows 3.x Client

Yes

Logs timestamps in trace statements.

None

 

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  3.0   (English)

Product Summary
Product: SNA Server Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: 20 Nov 1996
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 3.0 Service Pack 3, NVALERT and AFTP software updates, or SNA Server 3.0 Service Pack 4.0
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: (see below)
Last Updated: 21 Sep 1999
Product Details

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.

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.

Component

Uses Dates

Use of Dates

Known Issues

Administration

Yes

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Yes

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Yes

Logs timestamp for Netview events according to IBM specifications.  Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward.

A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

 

 

AFTP (File Transfer)

Yes

Displays and sets modification and access times on files transferred between systems

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file was created on 3/18/2001, the AFTP Server would display a date of 3/18/101. A software update for Intel and Alpha platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

SNA Gateway

Yes

Logs timestamps in trace statements.  Uses timers for internal scheduling.

None

Setup

Yes

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Yes

Uses FileTimeToDosDateTime.  Valid till 12/31/2107 Current versions of OS/400 (V4R2) only allow dates to 2053.

None

RASSNA (RAS over a SNA network)

Yes

Logs timestamps in trace statements.

None

TN3270

Yes

Logs timestamps in trace statements.

None

TN5250

Yes

Logs timestamps in trace statements.

None

Print Server

Yes

Logs timestamps in trace statements.

None

Windows 95 Client

Yes

Logs timestamps in trace statements.

None

MS-DOS Client

Yes

Logs timestamps in trace statements.

None

Windows 3.x Client

Yes

Logs timestamps in trace statements.

None



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.




Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  3.0   (Japanese)

Product Summary
Product: SNA Server Version: 3.0 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 21 Feb 1997
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 3.0 Service Pack 3, NVALERT and AFTP software updates, or SNA Server 3.0 Service Pack 4.0
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: See below
Last Updated: 21 Sep 1999
Product Details

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 or 4 are available at
ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/.


NVALERT and AFTP Software update available below.


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.

Component

Uses Dates

Use of Dates

Known Issues

Administration

Yes

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Yes

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Yes

Logs timestamp for Netview events according to IBM specifications.  Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward.

A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

 

 

AFTP (File Transfer)

Yes

Displays and sets modification and access times on files transferred between systems

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file was created on 3/18/2001, the AFTP Server would display a date of 3/18/101. A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

SNA Gateway

Yes

Logs timestamps in trace statements.  Uses timers for internal scheduling.

None

Setup

Yes

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Yes

Uses FileTimeToDosDateTime.  Valid till 12/31/2107 Current versions of OS/400 (V4R2) only allow dates to 2053.

None

RASSNA (RAS over a SNA network)

Yes

Logs timestamps in trace statements.

None

TN3270

Yes

Logs timestamps in trace statements.

None

TN5250

Yes

Logs timestamps in trace statements.

None

Print Server

Yes

Logs timestamps in trace statements.

None

Windows 95 Client

Yes

Logs timestamps in trace statements.

None

MS-DOS Client

Yes

Logs timestamps in trace statements.

None

Windows 3.x Client

Yes

Logs timestamps in trace statements.

None


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.




Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  4.0 SP1   (English)

Product Summary
Product: SNA Server Version: 4.0 SP1 Category:Compliant*
Language: English OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 4.0 SP1; MDAC 2.0 Service Pack 2; upgrades for NValert, and AFTP
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: See below
Last Updated: 25 Oct 1999
Product Details

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,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )

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.

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward.

A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

AFTP (File Transfer)

Displays and sets modification and access times on files transferred between systems

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file was created on 3/18/2001, the AFTP Server would display a date of 3/18/101. A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna- public/fixes/

SNA Gateway

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime. Valid till 12/31/2107

None

RASSNA (RAS over a SNA network)

Logs timestamps in trace statements.

None

TN3270

Logs timestamps in trace statements.

None

TN5250

Logs timestamps in trace statements.

None

Print Server

Logs timestamps in trace statements.

None

OLE DB Provider

Converts date/time data. Depends on ADO and OLEDB services.

None

COM Transaction Integrator

Dates converted using four digit formats. Valid till 12/31/9999.

None

Windows 9x Client

Logs timestamps in trace statements.

None

MS-DOS Client

Logs timestamps in trace statements.

None

Windows 3.x Client

Logs timestamps in trace statements.

None

ODBC Driver

Converts date time data.

None

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  4.0 SP1   (Japanese)

Product Summary
Product: SNA Server Version: 4.0 SP1 Category:Compliant*
Language: Japanese OS: Win NT Release Date: N/A
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 4.0 SP1; MDAC 2.0 Service Pack 2; software upgrade for NValert and AFTP
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: See below
Last Updated: 21 Sep 1999
Product Details

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,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )

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.

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward.

A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

AFTP (File Transfer)

Displays and sets modification and access times on files transferred between systems.

The AFTP Server service does not show the file dates correctly for year 2000 and beyond. For example, if a file was created on 3/18/2001, the AFTP Server would display a date of 3/18/101. A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna- public/fixes/

SNA Gateway

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime. Valid till 12/31/2107

None

RASSNA (RAS over a SNA network)

Logs timestamps in trace statements.

None

TN3270

Logs timestamps in trace statements.

None

TN5250

Logs timestamps in trace statements.

None

Print Server

Logs timestamps in trace statements.

None

OLE DB Provider

Converts date/time data. Depends on ADO and OLEDB services.

None

COM Transaction Integrator

Dates converted using four digit formats. Valid till 12/31/9999.

None

Windows 9x Client

Logs timestamps in trace statements.

None

MS-DOS Client

Logs timestamps in trace statements.

None

Windows 3.x Client

Logs timestamps in trace statements.

None

ODBC Driver

Converts date time data.

None

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  4.0 SP2   (English)

Product Summary
Product: SNA Server Version: 4.0 SP2 Category:Compliant*
Language: English OS: Win NT Release Date: 05 Dec 1997
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 4.0 Service Pack 2; MDAC 2.11.3711.11 or later
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: {See below}
Last Updated: 21 Sep 1999
Product Details

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.

Clock Dependencies: System Clock,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )

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.

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

None

AFTP (File Transfer)

Displays and sets modification and access times on files transferred between systems.

None

SNA Gateway

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime. Valid till 12/31/2107

None

RASSNA (RAS over a SNA network)

Logs timestamps in trace statements.

None

TN3270

Logs timestamps in trace statements.

None

TN5250

Logs timestamps in trace statements.

None

Print Server

Logs timestamps in trace statements.

None

OLE DB Provider

Converts date/time data. Depends on ADO and OLEDB services.

None

COM Transaction Integrator

Dates converted using four digit formats. Valid till 12/31/9999.

None

Windows 9x Client

Logs timestamps in trace statements.

None

MS-DOS Client

Logs timestamps in trace statements.

None

Windows 3.x Client

Logs timestamps in trace statements.

None

ODBC Driver

Converts date time data.

None

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  4.0 SP2   (Japanese)

Product Summary
Product: SNA Server Version: 4.0 SP2 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 20 Mar 1998
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: SNA Server 4.0 Service Pack 2; MDAC 2.11.3711.11 or later
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: See below
Last Updated: 21 Sep 1999
Product Details

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.

Clock Dependencies: System Clock,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )


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_view68559EN.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.

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

None

AFTP (File Transfer)

Displays and sets modification and access times on files transferred between systems.

None

SNA Gateway

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime. Valid till 12/31/2107

None

RASSNA (RAS over a SNA network)

Logs timestamps in trace statements.

None

TN3270

Logs timestamps in trace statements.

None

TN5250

Logs timestamps in trace statements.

None

Print Server

Logs timestamps in trace statements.

None

OLE DB Provider

Converts date/time data. Depends on ADO and OLEDB services.

None

COM Transaction Integrator

Dates converted using four digit formats. Valid till 12/31/9999.

None

Windows 9x Client

Logs timestamps in trace statements.

None

MS-DOS Client

Logs timestamps in trace statements.

None

Windows 3.x Client

Logs timestamps in trace statements.

None

ODBC Driver

Converts date time data.

None

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.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Server  4.0 SP3   (English)

Product Summary
Product: SNA Server Version: 4.0 SP3 Category:Compliant*
Language: English OS: Win NT Release Date: 05 Dec 1997
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: MDAC 2.1.2.4202.3 (GA) or later.
Product Dependencies: Windows NT 4.0 Service Pack 4
Clock Dependencies: System Clock, mktime( ), asctime( ), ctime( ), FileTimeToSystemTime( ), GetLocalTime( ), GetSystemTime( ), gmtime( ), localtime( ), mktime( ), SystemTimeToFileTime( ), time( )
Last Updated: 05 Oct 1999
Product Details

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.

Clock Dependencies: System Clock,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )

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.

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications. Years are represented in years since 1900.

None

AFTP (File Transfer)

Displays and sets modification and access times on files transferred between systems.

None

SNA Gateway

Logs timestamps in trace statements. Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime. Valid until 12/31/2107

None

RASSNA (RAS over a SNA network)

Logs timestamps in trace statements.

None

TN3270

Logs timestamps in trace statements.

None

TN5250

Logs timestamps in trace statements.

None

Print Server

Logs timestamps in trace statements.

None

OLE DB Provider

Converts date/time data. Depends on ADO and OLEDB services.

None

COM Transaction Integrator

Dates converted using four digit formats. Valid untill 12/31/9999.

None

Windows 9x Client

Logs timestamps in trace statements.

None

MS-DOS Client

Logs timestamps in trace statements.

None

Windows 3.x Client

Logs timestamps in trace statements.

None

ODBC Driver

Converts date time data.

None

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.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Workstation  3.0   (English)

Product Summary
Product: SNA Workstation Version: 3.0 Category:Compliant*
Language: English OS: Win NT Release Date: 20 Nov 1996
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: NVALERT software update
Product Dependencies: Windows NT Workstation 4.0 Service Pack 4
Clock Dependencies: {see below}
Last Updated: 21 Sep 1999
Product Details

Clock Dependencies:
System Clock,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )

            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.

Component

Uses Dates

Use of Dates

Known Issues

Administration

Yes

Displays the Hour/Min/Sec that Active sessions started

None

     

     

     

 

Client/Server Protocol

Yes

Logs the Hour/Min/Sec that Active sessions started to Administration

None

     

     

     

 

Netview

Yes

Logs timestamp for Netview events according to IBM specifications.  Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward. A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

     

     

     

     

SNA Gateway

Yes

Logs timestamps in trace statements.  Uses timers for internal scheduling.

None

     

     

     

     

Setup

Yes

Compares file timestamps between system and files to be installed.

None

     

     

     

 

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Yes

Uses FileTimeToDosDateTime.  Valid till 12/31/2107 Current versions of OS/400 (V4R2) only allow dates to 2053.

None


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 Workstation and should be looked at carefully by the user.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SNA Workstation  4.0   (English)

Product Summary
Product: SNA Workstation Version: 4.0 Category:Compliant*
Language: English OS: Win NT Release Date: 05 Dec 1997
Operational Range: 01 Jan 1970 - 31 Dec 2035
Prerequisites: NVALERT Software Update
Product Dependencies: Windows NT Workstation 4.0 Service Pack 4
Clock Dependencies: {See below}
Last Updated: 21 Sep 1999
Product Details

Clock Dependencies:

System Clock,
mktime( )
asctime( )
ctime( )
FileTimeToSystemTime( )
GetLocalTime( )
GetSystemTime( )
gmtime( )
localtime( )
mktime( )
SystemTimeToFileTime( )
time( )
oleaut32.dll


Prerequisites

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.  

Component

Use of Dates

Known Issues

Administration

Displays the Hour/Min/Sec that Active sessions started

None

Client/Server Protocol

Logs the Hour/Min/Sec that Active sessions started to Administration

None

Netview

Logs timestamp for Netview events according to IBM specifications.  Years are represented in years since 1900.

NVALERT formats local date/time (X'10) subvector incorrectly for year 2000. The one-byte year field within this subvector should contain the last two digits of the date. For the year 2000, this should be set to 00. However, NVALERT incorrectly sets the date field for year 2000 onward. A software update for Alpha and Intel platforms for this issue is available at ftp://ftp.microsoft.com/bussys/winnt/sna-public/fixes/

 

 

 

     

     

     

SNA Gateway

Logs timestamps in trace statements.  Uses timers for internal scheduling.

None

Setup

Compares file timestamps between system and files to be installed.

None

Shared Folders Gateway (Allows access to OS/400 files as FAT file system)

Uses FileTimeToDosDateTime.  Valid till 12/31/2107

None


2 digit shortcuts
Not applicable, there is no user entry of dates.

What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?
Not applicable, there is no user entry of dates.

Common pitfalls for use or testing of SNA Workstation
None identified.  Data transferred through SNA Workstation 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 Workstation and should be reviewed by the user.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.0   (English)

Product Summary
Product: SQL Server Version: 6.0 Category:Compliant*#
Language: English OS: 32-Bit Win Release Date: 01 Jul 1995
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: SQL 6.0 Service Pack 3
Product Dependencies: Microsoft Data Access Components (MDAC), Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System clock
Last Updated: 27 Oct 1999
Product Details

Prerequisites: SQL 6.0 Service Pack 3 is available at http://support.microsoft.com/support/downloads/.

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, ISQL/w, Security Manager, Client Configuration Utility, Service Manager and SQL Server Executive. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be in the 2000s and values greater than or equal to 50 are parsed in the 1900s. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

What are the issues with SQL 6.0 Service Pack 3? Testing of SQL 6.0 Service Pack 3 has identified the following issues.

    • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides.
    • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP.
    • SQL Executive does not recognize year 2000 as a leap year.
    • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface.
    • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters.
    • If a database is dumped to a dump device on Jan. 1, 2000, or later, the creation date stored in the dump file header is set to NULL. When you use SQL Server Enterprise Manager to view the dumps stored in a dump device, no date is displayed for any dump created after Jan. 1, 2000.
    • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
      1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
      2. An INF file is used to specify the list of files to be installed.
      3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the problem) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.

Investigate front end application behavior using SQL Server as a backend and interaction with other applications.


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.0   (French)

Product Summary
Product: SQL Server Version: 6.0 Category:Compliant#
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System clock
Last Updated: 02 Nov 1999
Product Details

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, ISQL/w, Security Manager, Client Configuration Utility, Service Manager and SQL Server Executive. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be in the 2000s and values greater than or equal to 50 are parsed in the 1900s. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

Testing of SQL Server 6.0 has identified the following issues.

    • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides.
    • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP.
    • SQL Executive does not recognize year 2000 as a leap year.
    • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface.
    • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters.
    • If a database is dumped to a dump device on Jan. 1, 2000, or later, the creation date stored in the dump file header is set to NULL. When you use SQL Server Enterprise Manager to view the dumps stored in a dump device, no date is displayed for any dump created after Jan. 1, 2000.
    • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
      1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
      2. An INF file is used to specify the list of files to be installed.
      3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the problem) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.0   (German)

Product Summary
Product: SQL Server Version: 6.0 Category:Compliant#
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System clock
Last Updated: 02 Nov 1999
Product Details

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, ISQL/w, Security Manager, Client Configuration Utility, Service Manager and SQL Server Executive. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be in the 2000s and values greater than or equal to 50 are parsed in the 1900s. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

Testing of SQL Server 6.0 has identified the following issues.

    • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides.
    • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP.
    • SQL Executive does not recognize year 2000 as a leap year.
    • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface.
    • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters.
    • If a database is dumped to a dump device on Jan. 1, 2000, or later, the creation date stored in the dump file header is set to NULL. When you use SQL Server Enterprise Manager to view the dumps stored in a dump device, no date is displayed for any dump created after Jan. 1, 2000.
    • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
      1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
      2. An INF file is used to specify the list of files to be installed.
      3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the problem) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.0   (Japanese)

Product Summary
Product: SQL Server Version: 6.0 Category:Compliant*#
Language: Japanese OS: 32-Bit Win Release Date: 01 Jul 1995
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: SQL 6.0 Service Pack 3
Product Dependencies: ODBC Driver Manager, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System clock
Last Updated: 02 Nov 1999
Product Details

Prerequisites: SQL 6.0 Service Pack 3 for Japanese is available at http://www.microsoft.com/japan/bkoffice/ntsql/in_pack.htm

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, ISQL/w, Security Manager, Client Configuration Utility, Service Manager and SQL Server Executive. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be in the 2000s and values greater than or equal to 50 are parsed in the 1900s. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

What are the issues with SQL Server 6.0 Service Pack 3?Testing of SQL Server 6.0 Service Pack 3 has identified the following issues.

    • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides.
    • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP.
    • SQL Executive does not recognize year 2000 as a leap year.
    • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface.
    • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters.
    • If a database is dumped to a dump device on Jan. 1, 2000, or later, the creation date stored in the dump file header is set to NULL. When you use SQL Server Enterprise Manager to view the dumps stored in a dump device, no date is displayed for any dump created after Jan. 1, 2000.
    • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
      1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
      2. An INF file is used to specify the list of files to be installed.
      3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the problem) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.5   (English)

Product Summary
Product: SQL Server Version: 6.5 Category:Compliant*
Language: English OS: Win NT Release Date: 01 Apr 1996
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC)
Product Dependencies: Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 27 Oct 1999
Product Details

 

 

This information applies to Standard, Enterprise, Developer, and Small Business Server editions, as well as to the SQL Server edition provided with the SQL Server Workstation product.

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 SQL Server 6.5 Service Pack 5 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.

Recommendations to meet compliance:

It is recommended to update SQL Server to Service Pack 5 or higher to meet Year 2000 compliance requirements. The Service Pack 5 download is available at http://support.microsoft.com/support/downloads/

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 6.5 Service Pack 5 provides an optional installation for Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, we recommend that you install MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

SQL Server 6.5 Setup installs a Microsoft Foundation Classes (MFC) module Mfc40.dll into the SQL Server \Binn directory. The version of this module installed by SQL Server 6.5 has a Year 2000 issue with its function COleDatetime. MFC is not used by the SQL Server database engine, but the SQL Server Administrative Tools and Microsoft Distributed Transaction Coordinator (MS DTC) both use the MFC API. SQL Server code reviews have not identified any SQL Server product area that makes use of the COleDatetime function. While non-SQL Server applications typically load an instance of MFC from the system directory, there is a chance that an application could load the dll from the SQL Server binn directory if the application is either launched from the Binn directory or no other instances of MFC exist on the computer. Such applications are potentially exposed to the Year 2000 issue. Microsoft recommends searching for all instances of MFC and replacing all of them with a remediated version. Download and installation instructions are provided in Knowledge Base Article Q242378.

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, SQL Trace, ISQL/w, Security Manager, Client Configuration Utility, Service Manager, SQL Server Executive, Web Assistant and the SQL Maintenance Wizard. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for two digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The cutoff date observed by SQL Server 6.5 is 49, this cannot be configured or altered. The cutoff date used by SQL Server 7.0 can be configured, for more information see the Year 2000 document for SQL Server 7.0.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be 20XX and values greater than or equal to 50 are parsed 19XX. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

List of issues addressed by SQL Server 6.5 Service Pack 5.

  • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides. Fixed in SQL Server, Service Pack 5 and higher.
  • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP. Fixed in SQL Server, Service Pack 5 and higher.
  • SQL Executive does not recognize year 2000 as a leap year. Fixed in SQL Server 6.5, Service Pack 2 and higher.
  • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface. Fix is expected in SQL Server, Service Pack 5 and higher. Web Assistant does not allow scheduling a task in year 2000 and beyond. Workaround is to use the underlying stored procedure SP_MAKEWEBTASK, not the user interface. Fixed in SQL Server, Service Pack 5 and higher.
  • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters. Fixed in SQL Server, Service Pack 5 and higher.
  • The Microsoft Query client tool, an application shared by several Microsoft products accepts 2-digit year date formatting for the ODBC query, but assumes a twentieth century date. To avoid this, use 4-digit years for queries based upon date data in MS Query or use other client tools provided with SQL Server like ISQL/w or Enterprise Manager. Fixed in SQL Server, Service Pack 5 and higher.
  • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
    1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
    2. An INF file is used to specify the list of files to be installed.
    3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the issue) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

On Windows NT 4.0, Windows 95, and Windows 98, ODBC versions 3.0 and higher are provided either as part of Operating System Upgrades or Service Packs. For further compliance information, on see ODBC year 2000 compliance. For further information on ODBC and Microsoft Data Access Components, see http://www.microsoft.com/data/.

Microsoft Data Access Components version 2.1 (MDAC 2.1) are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The ODBC version provided herein is 3.51. SQL server customers on Windows NT 4, Windows 95 and Windows 98 who wish to upgrade from ODBC 2.5 should use MDAC 2.1.

SQL Server customers on Windows NT 3.51 who wish to upgrade from ODBC 2.5 should use the ODBC 3.0 setup, odbc3brz.exe, which will be available shortly from http://www.microsoft.com/data/. ODBC 3.0 is not available for the Win16 platform.

  • If the user has optionally installed replication to non-SQL Server datasources using the Microsoft ODBC Desktop Drivers, the Microsoft Jet database engine is being used, which is also used by Microsoft Access 95 (7.0). For Year2000 status consult Microsoft Access 95 (7.0). MDAC 2.1 are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The Jet version provided in the MDAC 2.1 release is Jet 4.0. Jet 3.51 for the NT 3.51 platform is available from odbc3brz.exe mentioned above.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.5   (French)

Product Summary
Product: SQL Server Version: 6.5 Category:Compliant*
Language: French OS: Win NT Release Date: 01 Jun 1996
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC)
Product Dependencies: Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 27 Oct 1999
Product Details

 

 

This information applies to Standard, Enterprise, Developer, and Small Business Server editions, as well as to the SQL Server edition provided with the SQL Server Workstation product.

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 SQL Server 6.5 Service Pack 5 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.

Recommendations to meet compliance:

It is recommended to update SQL Server to Service Pack 5 or higher to meet Year 2000 compliance requirements. The Service Pack 5 download is available at http://support.microsoft.com/support/downloads/

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 6.5 Service Pack 5 provides an optional installation for Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, we recommend that you install MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

SQL Server 6.5 Setup installs a Microsoft Foundation Classes (MFC) module Mfc40.dll into the SQL Server \Binn directory. The version of this module installed by SQL Server 6.5 has a Year 2000 issue with its function COleDatetime. MFC is not used by the SQL Server database engine, but the SQL Server Administrative Tools and Microsoft Distributed Transaction Coordinator (MS DTC) both use the MFC API. SQL Server code reviews have not identified any SQL Server product area that makes use of the COleDatetime function. While non-SQL Server applications typically load an instance of MFC from the system directory, there is a chance that an application could load the dll from the SQL Server binn directory if the application is either launched from the Binn directory or no other instances of MFC exist on the computer. Such applications are potentially exposed to the Year 2000 issue. Microsoft recommends searching for all instances of MFC and replacing all of them with a remediated version. Download and installation instructions are provided in Knowledge Base Article Q242378.

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, SQL Trace, ISQL/w, Security Manager, Client Configuration Utility, Service Manager, SQL Server Executive, Web Assistant and the SQL Maintenance Wizard. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for two digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The cutoff date observed by SQL Server 6.5 is 49, this cannot be configured or altered. The cutoff date used by SQL Server 7.0 can be configured, for more information see the Year 2000 document for SQL Server 7.0.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be 20XX and values greater than or equal to 50 are parsed 19XX. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

List of issues addressed by SQL Server 6.5 Service Pack 5.

  • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides. Fixed in SQL Server, Service Pack 5 and higher.
  • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP. Fixed in SQL Server, Service Pack 5 and higher.
  • SQL Executive does not recognize year 2000 as a leap year. Fixed in SQL Server 6.5, Service Pack 2 and higher.
  • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface. Fix is expected in SQL Server, Service Pack 5 and higher. Web Assistant does not allow scheduling a task in year 2000 and beyond. Workaround is to use the underlying stored procedure SP_MAKEWEBTASK, not the user interface. Fixed in SQL Server, Service Pack 5 and higher.
  • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters. Fixed in SQL Server, Service Pack 5 and higher.
  • The Microsoft Query client tool, an application shared by several Microsoft products accepts 2-digit year date formatting for the ODBC query, but assumes a twentieth century date. To avoid this, use 4-digit years for queries based upon date data in MS Query or use other client tools provided with SQL Server like ISQL/w or Enterprise Manager. Fixed in SQL Server, Service Pack 5 and higher.
  • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
    1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
    2. An INF file is used to specify the list of files to be installed.
    3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the issue) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

On Windows NT 4.0, Windows 95, and Windows 98, ODBC versions 3.0 and higher are provided either as part of Operating System Upgrades or Service Packs. For further compliance information, on see ODBC year 2000 compliance. For further information on ODBC and Microsoft Data Access Components, see http://www.microsoft.com/data/.

Microsoft Data Access Components version 2.1 (MDAC 2.1) are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The ODBC version provided herein is 3.51. SQL server customers on Windows NT 4, Windows 95 and Windows 98 who wish to upgrade from ODBC 2.5 should use MDAC 2.1.

SQL Server customers on Windows NT 3.51 who wish to upgrade from ODBC 2.5 should use the ODBC 3.0 setup, odbc3brz.exe, which will be available shortly from http://www.microsoft.com/data/. ODBC 3.0 is not available for the Win16 platform.

  • If the user has optionally installed replication to non-SQL Server datasources using the Microsoft ODBC Desktop Drivers, the Microsoft Jet database engine is being used, which is also used by Microsoft Access 95 (7.0). For Year2000 status consult Microsoft Access 95 (7.0). MDAC 2.1 are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The Jet version provided in the MDAC 2.1 release is Jet 4.0. Jet 3.51 for the NT 3.51 platform is available from odbc3brz.exe mentioned above.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.5   (German)

Product Summary
Product: SQL Server Version: 6.5 Category:Compliant*
Language: German OS: Win NT Release Date: 01 Jun 1996
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC)
Product Dependencies: Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 27 Oct 1999
Product Details

 

 

This information applies to Standard, Enterprise, Developer, and Small Business Server editions, as well as to the SQL Server edition provided with the SQL Server Workstation product.

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 SQL Server 6.5 Service Pack 5 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.

Recommendations to meet compliance:

It is recommended to update SQL Server to Service Pack 5 or higher to meet Year 2000 compliance requirements. The Service Pack 5 download is available at http://support.microsoft.com/support/downloads/

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 6.5 Service Pack 5 provides an optional installation for Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, we recommend that you install MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

SQL Server 6.5 Setup installs a Microsoft Foundation Classes (MFC) module Mfc40.dll into the SQL Server \Binn directory. The version of this module installed by SQL Server 6.5 has a Year 2000 issue with its function COleDatetime. MFC is not used by the SQL Server database engine, but the SQL Server Administrative Tools and Microsoft Distributed Transaction Coordinator (MS DTC) both use the MFC API. SQL Server code reviews have not identified any SQL Server product area that makes use of the COleDatetime function. While non-SQL Server applications typically load an instance of MFC from the system directory, there is a chance that an application could load the dll from the SQL Server binn directory if the application is either launched from the Binn directory or no other instances of MFC exist on the computer. Such applications are potentially exposed to the Year 2000 issue. Microsoft recommends searching for all instances of MFC and replacing all of them with a remediated version. Download and installation instructions are provided in Knowledge Base Article Q242378.

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, SQL Trace, ISQL/w, Security Manager, Client Configuration Utility, Service Manager, SQL Server Executive, Web Assistant and the SQL Maintenance Wizard. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for two digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The cutoff date observed by SQL Server 6.5 is 49, this cannot be configured or altered. The cutoff date used by SQL Server 7.0 can be configured, for more information see the Year 2000 document for SQL Server 7.0.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be 20XX and values greater than or equal to 50 are parsed 19XX. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

List of issues addressed by SQL Server 6.5 Service Pack 5.

  • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides. Fixed in SQL Server, Service Pack 5 and higher.
  • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP. Fixed in SQL Server, Service Pack 5 and higher.
  • SQL Executive does not recognize year 2000 as a leap year. Fixed in SQL Server 6.5, Service Pack 2 and higher.
  • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface. Fix is expected in SQL Server, Service Pack 5 and higher. Web Assistant does not allow scheduling a task in year 2000 and beyond. Workaround is to use the underlying stored procedure SP_MAKEWEBTASK, not the user interface. Fixed in SQL Server, Service Pack 5 and higher.
  • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters. Fixed in SQL Server, Service Pack 5 and higher.
  • The Microsoft Query client tool, an application shared by several Microsoft products accepts 2-digit year date formatting for the ODBC query, but assumes a twentieth century date. To avoid this, use 4-digit years for queries based upon date data in MS Query or use other client tools provided with SQL Server like ISQL/w or Enterprise Manager. Fixed in SQL Server, Service Pack 5 and higher.
  • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
    1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
    2. An INF file is used to specify the list of files to be installed.
    3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the issue) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

On Windows NT 4.0, Windows 95, and Windows 98, ODBC versions 3.0 and higher are provided either as part of Operating System Upgrades or Service Packs. For further compliance information, on see ODBC year 2000 compliance. For further information on ODBC and Microsoft Data Access Components, see http://www.microsoft.com/data/.

Microsoft Data Access Components version 2.1 (MDAC 2.1) are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The ODBC version provided herein is 3.51. SQL server customers on Windows NT 4, Windows 95 and Windows 98 who wish to upgrade from ODBC 2.5 should use MDAC 2.1.

SQL Server customers on Windows NT 3.51 who wish to upgrade from ODBC 2.5 should use the ODBC 3.0 setup, odbc3brz.exe, which will be available shortly from http://www.microsoft.com/data/. ODBC 3.0 is not available for the Win16 platform.

  • If the user has optionally installed replication to non-SQL Server datasources using the Microsoft ODBC Desktop Drivers, the Microsoft Jet database engine is being used, which is also used by Microsoft Access 95 (7.0). For Year2000 status consult Microsoft Access 95 (7.0). MDAC 2.1 are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The Jet version provided in the MDAC 2.1 release is Jet 4.0. Jet 3.51 for the NT 3.51 platform is available from odbc3brz.exe mentioned above.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  6.5   (Japanese)

Product Summary
Product: SQL Server Version: 6.5 Category:Compliant*
Language: Japanese OS: Win NT Release Date: 30 Aug 1996
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: Service Pack 5 or higher, Microsoft Data Access Components (MDAC), Microsoft Foundation Classes (MFC)
Product Dependencies: Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 27 Oct 1999
Product Details

 

 

This information applies to Standard, Enterprise, Developer, and Small Business Server editions, as well as to the SQL Server edition provided with the SQL Server Workstation product.

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 SQL Server 6.5 Service Pack 5 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.

Recommendations to meet compliance:

It is recommended to update SQL Server to Service Pack 5 or higher to meet Year 2000 compliance requirements. The Service Pack 5 download is available at http://support.microsoft.com/support/downloads/

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 6.5 Service Pack 5 provides an optional installation for Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, we recommend that you install MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

SQL Server 6.5 Setup installs a Microsoft Foundation Classes (MFC) module Mfc40.dll into the SQL Server \Binn directory. The version of this module installed by SQL Server 6.5 has a Year 2000 issue with its function COleDatetime. MFC is not used by the SQL Server database engine, but the SQL Server Administrative Tools and Microsoft Distributed Transaction Coordinator (MS DTC) both use the MFC API. SQL Server code reviews have not identified any SQL Server product area that makes use of the COleDatetime function. While non-SQL Server applications typically load an instance of MFC from the system directory, there is a chance that an application could load the dll from the SQL Server binn directory if the application is either launched from the Binn directory or no other instances of MFC exist on the computer. Such applications are potentially exposed to the Year 2000 issue. Microsoft recommends searching for all instances of MFC and replacing all of them with a remediated version. Download and installation instructions are provided in Knowledge Base Article Q242378.

How the product handles dates:

1) Server:

SQL Server has two date/time datatypes: datetime and smalldatetime. The datetime datatype is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, to December 31, 9999, to an accuracy of one three-hundredths of a second (3.33 milliseconds).

The smalldatetime datatype is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either datatype allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. If only 2 digits are specified, values less than 50 are interpreted as 20yy, and values greater than or equal to 50 are interpreted as 19yy. For example, if users specify "03", the date is stored as 2003. If users specify "82", the date is stored as 1982.

2) SQL Administration Tools:

SQL Server Administration Tools include SQL Enterprise Manager, SQL Trace, ISQL/w, Security Manager, Client Configuration Utility, Service Manager, SQL Server Executive, Web Assistant and the SQL Maintenance Wizard. Several of listed tools allow display and/or input of date information:

Date display:

Uses either SQL Server Engine formatting or Windows NT Control Panel Settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the Server include Stored Procedures, SQLOLE, DB-Library, SQL Server ODBC driver and Net-Libraries. Plausibility validation of entered dates happens mostly on SQL Engine Level for datetime data types. SQL Server Executive, the Task and Alert scheduling engine of SQL Server, represents an exception: Date information for scheduled tasks is stored in integer datatypes. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using SQL Servers ISDATE() function within stored procedures prior to storage in the database.

3) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for two digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The cutoff date observed by SQL Server 6.5 is 49, this cannot be configured or altered. The cutoff date used by SQL Server 7.0 can be configured, for more information see the Year 2000 document for SQL Server 7.0.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying two-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support four-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

Two-digit shortcut handling:

The SQL Server Engine allows dates to be input using 2-digit years in datetime data types. Regardless of whether the date is input as a 2-digit or 4-digit year, it is stored the same as noted above. When using a 2-digit year, values less than 50 are assumed to be 20XX and values greater than or equal to 50 are parsed 19XX. For example, a 2-digit year of "25" is stored as "2025", while a 2-digit year of "50" is stored as "1950".

List of issues addressed by SQL Server 6.5 Service Pack 5.

  • The EXPIREDATE clause for DUMP DATABASE does not properly handle dates greater or equal to 2000. EXPIREDATE is used to say when its ok to reuse backup media. Encountering this issue does not impact general operation of SQL Server. The impact is limited to accidental overwrites of backup media and not providing the extra safety check that EXPIREDATE provides. Fixed in SQL Server, Service Pack 5 and higher.
  • The RETAINDAYS clause for DUMP DATABASE does not work properly when the system time has moved beyond 12/31/99. Impact is that an existing dump cannot be overwritten, workaround is to manually delete the pre-existing dump image before attempting the DUMP. Fixed in SQL Server, Service Pack 5 and higher.
  • SQL Executive does not recognize year 2000 as a leap year. Fixed in SQL Server 6.5, Service Pack 2 and higher.
  • Task Manager user interface spin box does not recognize year 2000 as a leap year. The workaround for this is to schedule the task directly via executing the stored procedure, not the user interface. Fix is expected in SQL Server, Service Pack 5 and higher. Web Assistant does not allow scheduling a task in year 2000 and beyond. Workaround is to use the underlying stored procedure SP_MAKEWEBTASK, not the user interface. Fixed in SQL Server, Service Pack 5 and higher.
  • SP_ADDTASK, SP_PURGEHISTORY and SP_UPDATEALERT stored procedures allow several invalid dates as input parameters. This has no consequences as long as valid dates are used as input parameters. Fixed in SQL Server, Service Pack 5 and higher.
  • The Microsoft Query client tool, an application shared by several Microsoft products accepts 2-digit year date formatting for the ODBC query, but assumes a twentieth century date. To avoid this, use 4-digit years for queries based upon date data in MS Query or use other client tools provided with SQL Server like ISQL/w or Enterprise Manager. Fixed in SQL Server, Service Pack 5 and higher.
  • Two APIs in ODBC 2.5 are affected by Year 2000 issues. The SQLInstallDriver and SQLInstallODBC APIs are used to write custom setups for ODBC drivers. If the following conditions are met, a wrong version of a file may be installed:
    1. The Setup is written using the APIs SQLInstallDriver or SQLInstallODBC
    2. An INF file is used to specify the list of files to be installed.
    3. The filelist information in the INF file includes file date but not the file version.

Both the Win32 and the Win16 APIs are affected by this issue. Note, the SQL Server ODBC installs provided with SQL Server 6.5 itself use both, date and version information and are therefore not affected.

The SQLInstallODBC API was discontinued after ODBC 2.5. SQLInstallDriver still exists, but the option to use an INF file (the source of the issue) was removed in ODBC 3.0. Instead a new preferred API, SQLInstallDriverEx, was added.

On Windows NT 4.0, Windows 95, and Windows 98, ODBC versions 3.0 and higher are provided either as part of Operating System Upgrades or Service Packs. For further compliance information, on see ODBC year 2000 compliance. For further information on ODBC and Microsoft Data Access Components, see http://www.microsoft.com/data/.

Microsoft Data Access Components version 2.1 (MDAC 2.1) are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The ODBC version provided herein is 3.51. SQL server customers on Windows NT 4, Windows 95 and Windows 98 who wish to upgrade from ODBC 2.5 should use MDAC 2.1.

SQL Server customers on Windows NT 3.51 who wish to upgrade from ODBC 2.5 should use the ODBC 3.0 setup, odbc3brz.exe, which will be available shortly from http://www.microsoft.com/data/. ODBC 3.0 is not available for the Win16 platform.

  • If the user has optionally installed replication to non-SQL Server datasources using the Microsoft ODBC Desktop Drivers, the Microsoft Jet database engine is being used, which is also used by Microsoft Access 95 (7.0). For Year2000 status consult Microsoft Access 95 (7.0). MDAC 2.1 are provided as part of SQL Server 6.5 Service Pack 5 and are identical to the versions shipping in SQL Server 7.0. The Jet version provided in the MDAC 2.1 release is Jet 4.0. Jet 3.51 for the NT 3.51 platform is available from odbc3brz.exe mentioned above.

Testing guidelines and recommendations:

    • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to datetime.
    • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
    • Investigate front end application behavior using SQL Server as a backend and interaction with other applications.

 

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  7.0   (English)

Product Summary
Product: SQL Server Version: 7.0 Category:Compliant
Language: English OS: Win NT Release Date: 01 Nov 1998
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System clock
Last Updated: 11 Nov 1999
Product Details

This information applies to the Standard, Enterprise, Developer, Small Business, and Evaluation editions of SQL Server 7.0.

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 SQL Server 7.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.

 

Recommendations to meet compliance

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 7.0 installs Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, Microsoft recommends installing MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

How the product handles dates:

1) Server:

SQL Server has two date/time data types: datetime and smalldatetime. The datetime data type is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes are for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, through December 31, 9999, to an accuracy of one three-hundredth of a second (3.33 milliseconds).

Smalldatetime is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either data type allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. The "two-digit year cutoff" configuration option defines how SQL Server 7.0 expands a 2-digit year to four digits. The option is specified as a 4-digit year, the default is 2049. If only two digits are specified for a year, and they are less than or equal to the last two digits of the 2-digit year cutoff option, the date is stored as being in the same century as the option. If the specified two digits are greater than the last two digits of the 2-digit year cutoff option, the date is stored as being in the century before the one specified in the option. For example, if the 2-digit year cutoff option is left at its default of 2049, the value 49 is stored as 2049 and 50 is stored as 1950. If the 2-digit year cutoff option is set to 2029, the value 29 is stored as 2029 and 30 is stored as 1930. Earlier versions of SQL Server do not have a configurable 2-digit year cutoff option; they operate using a cutoff of 2049.

2) SQL Administration Tools:

SQL Server administration tools include SQL Server Enterprise Manager, SQL Server Profiler, SQL Server Query Analyzer, SQL Server Service Manager, Client Network Utility, Server Network Utility, SQL Server Agent, and more than 25 wizards. Several of these tools allow display and/or input of date information.

Date display:

Uses either SQL Server Engine formatting or Microsoft Windows NT® Control Panel settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the server include Transact-SQL, SQL Server Distributed Management Framework objects, OLE DB Provider for SQL Server, SQL Server ODBC driver, DB-Library, and Net-Libraries. Plausibility validation of entered dates happens mostly at the Microsoft Data Engine level for datetime and smalldatetime data types. SQL Server Agent, the job and alert scheduling engine of SQL Server, represents an exception: date information for scheduled jobs is stored in integer data types. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using the SQL Server ISDATE() function within stored procedures prior to storage in the database.

3) SQL Data Management Objects

Some SQL Data Management Objects have properties that represent dates. These properties are implemented as long integers in which dates are represented by numbers having the pattern YYYYMMDD. For example, the date April 19, 1998 is represented by the number 19980419.

4) Data Transformation Services

Data Transformation Services (DTS) supports transformations that map source string columns (DBTYPE_STR or DBTYPE_WSTR) to destination date columns (DBTYPE_DATE). The date portion of the strings in the source columns must be in the OLE DB format of YYYY-MM-DD. Transformations can also map source date columns to destination string columns, in which case the date portion is converted to a string having the OLE DB format of YYYY-MM-DD. For example, the OLE DB format for April 19, 1998 is 1998-04-19. Transformations using scripts, such as Microsoft ActiveX® or Microsoft Visual Basic® scripts, can also use the CDate() function for inputting dates.

5) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for 2-digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The default cutoff date observed by SQL Server 7.0 is 49, this maintains compatibility with earlier versions of SQL Server. If you are not concerned with compatibility with earlier versions of SQL Server, you can configure SQL Server to also use 29 as the cutoff date. For more information, see the SQL Server 7.0 Books Online.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying 2-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support 4-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

How the applications and components shipped with SQL Server 7.0 handle dates:

 

Microsoft English Query:

Date storage

Microsoft English Query does not store dates.

SQL generation

Date constants in generated SQL conditions use the generic date format YYYYMMDD. Year constants generated in SQL conditions use the format YYYY or YY, depending on a developer-controlled English Query setting on each year field. For fields marked to use the YY format, the century digits are simply omitted from the SQL condition.

Formatting

Dates in the testing tool are displayed using the ODBC text date format, which defaults to YYYY-MM-DD. ODBC can be configured to use regional settings instead.

Parsing on date entry

Dates can be input in questions using standard United States textual date formats. These include, but are not limited to:

    • Slash-formatted dates: (M)M/(D)D/(YY)YY
    • Text full dates: Month (D)D, (YY)YY
    • Text months: Month (YY)YY
    • Slash-formatted months: (M)M/(YY)YY

Two-digit shortcut handling

Microsoft English Query interprets years entered with a 2-digit shortcut as:

    • 1/1/00 through 12/31/29 is interpreted as 1/1/2000 through 12/31/2029.
    • 1/1/30 through 12/31/99 is interpreted as 1/1/1930 through 12/31/1999.

Microsoft OLAP Services:

 Date storage

Microsoft OLAP Services stores dates internally in the OLAP Services repository in accordance with the OLE DB for OLAP specification.

Formatting

The OLAP Services user interface does not include fields for date entries. Date information may be exposed through Decision Support Objects (DSO) and multidimensional expressions (MDX). These rely on the Year2000 compliance of the Microsoft Visual Basic® environment.

Processing queries and aggregations

Bounds checking and processing of queries and aggregations before, during, and after the rollover of January 1, 2000 have been verified and complete successfully.

Microsoft Repository:

 

Date storage

Repository accepts dates in the range January 1, 100 to December 31, 9999. It does not truncate the year to a 2-digit year so no reconversion is required at retrieval time. It stores the year in the form YYYY (in a DATE_STRUCT or TIMESTAMP_STRUCT structure, or the SQL Server datetime data type).

Formatting

Dates can be displayed in the format of MM/DD/YY, but this does not cause ambiguity because the dates are stored in SQL Server with 4-digit years.

Two digit shortcut handling

Applications must input dates using 4-digit years, attempting to input a 2-digit year results in an error. Engine-generated dates specify 4-digit years.

 

Microsoft Search Service:

The Microsoft Search Service that ships with SQL Server 7.0 works with data in character columns and has no dependencies on date data.

Testing guidelines and recommendations:

      • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to the datetime data type.
      • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
      • Investigate front-end application behavior using SQL Server as a backend and interaction with other applications.
      • SQL Server 7.0 supports a trace flag 8816 that records the 2-digit to 4-digit conversions done by the database engine. You can use this trace flag to determine if applications are sending SQL Server 2-digit years.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  7.0   (French)

Product Summary
Product: SQL Server Version: 7.0 Category:Compliant
Language: French OS: Win NT Release Date: 01 Nov 1998
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 11 Nov 1999
Product Details

This information applies to the Standard, Enterprise, Developer, Small Business, and Evaluation editions of SQL Server 7.0.

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 SQL Server 7.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.

 

Recommendations to meet compliance

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 7.0 installs Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, Microsoft recommends installing MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

How the product handles dates:

1) Server:

SQL Server has two date/time data types: datetime and smalldatetime. The datetime data type is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes are for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, through December 31, 9999, to an accuracy of one three-hundredth of a second (3.33 milliseconds).

Smalldatetime is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either data type allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. The "two-digit year cutoff" configuration option defines how SQL Server 7.0 expands a 2-digit year to four digits. The option is specified as a 4-digit year, the default is 2049. If only two digits are specified for a year, and they are less than or equal to the last two digits of the 2-digit year cutoff option, the date is stored as being in the same century as the option. If the specified two digits are greater than the last two digits of the 2-digit year cutoff option, the date is stored as being in the century before the one specified in the option. For example, if the 2-digit year cutoff option is left at its default of 2049, the value 49 is stored as 2049 and 50 is stored as 1950. If the 2-digit year cutoff option is set to 2029, the value 29 is stored as 2029 and 30 is stored as 1930. Earlier versions of SQL Server do not have a configurable 2-digit year cutoff option; they operate using a cutoff of 2049.

2) SQL Administration Tools:

SQL Server administration tools include SQL Server Enterprise Manager, SQL Server Profiler, SQL Server Query Analyzer, SQL Server Service Manager, Client Network Utility, Server Network Utility, SQL Server Agent, and more than 25 wizards. Several of these tools allow display and/or input of date information.

Date display:

Uses either SQL Server Engine formatting or Microsoft Windows NT® Control Panel settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the server include Transact-SQL, SQL Server Distributed Management Framework objects, OLE DB Provider for SQL Server, SQL Server ODBC driver, DB-Library, and Net-Libraries. Plausibility validation of entered dates happens mostly at the Microsoft Data Engine level for datetime and smalldatetime data types. SQL Server Agent, the job and alert scheduling engine of SQL Server, represents an exception: date information for scheduled jobs is stored in integer data types. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using the SQL Server ISDATE() function within stored procedures prior to storage in the database.

3) SQL Data Management Objects

Some SQL Data Management Objects have properties that represent dates. These properties are implemented as long integers in which dates are represented by numbers having the pattern YYYYMMDD. For example, the date April 19, 1998 is represented by the number 19980419.

4) Data Transformation Services

Data Transformation Services (DTS) supports transformations that map source string columns (DBTYPE_STR or DBTYPE_WSTR) to destination date columns (DBTYPE_DATE). The date portion of the strings in the source columns must be in the OLE DB format of YYYY-MM-DD. Transformations can also map source date columns to destination string columns, in which case the date portion is converted to a string having the OLE DB format of YYYY-MM-DD. For example, the OLE DB format for April 19, 1998 is 1998-04-19. Transformations using scripts, such as Microsoft ActiveX® or Microsoft Visual Basic® scripts, can also use the CDate() function for inputting dates.

5) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for 2-digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The default cutoff date observed by SQL Server 7.0 is 49, this maintains compatibility with earlier versions of SQL Server. If you are not concerned with compatibility with earlier versions of SQL Server, you can configure SQL Server to also use 29 as the cutoff date. For more information, see the SQL Server 7.0 Books Online.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying 2-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support 4-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

How the applications and components shipped with SQL Server 7.0 handle dates:

 

Microsoft English Query:

Date storage

Microsoft English Query does not store dates.

SQL generation

Date constants in generated SQL conditions use the generic date format YYYYMMDD. Year constants generated in SQL conditions use the format YYYY or YY, depending on a developer-controlled English Query setting on each year field. For fields marked to use the YY format, the century digits are simply omitted from the SQL condition.

Formatting

Dates in the testing tool are displayed using the ODBC text date format, which defaults to YYYY-MM-DD. ODBC can be configured to use regional settings instead.

Parsing on date entry

Dates can be input in questions using standard United States textual date formats. These include, but are not limited to:

    • Slash-formatted dates: (M)M/(D)D/(YY)YY
    • Text full dates: Month (D)D, (YY)YY
    • Text months: Month (YY)YY
    • Slash-formatted months: (M)M/(YY)YY

Two-digit shortcut handling

Microsoft English Query interprets years entered with a 2-digit shortcut as:

    • 1/1/00 through 12/31/29 is interpreted as 1/1/2000 through 12/31/2029.
    • 1/1/30 through 12/31/99 is interpreted as 1/1/1930 through 12/31/1999.

Microsoft OLAP Services:

 Date storage

Microsoft OLAP Services stores dates internally in the OLAP Services repository in accordance with the OLE DB for OLAP specification.

Formatting

The OLAP Services user interface does not include fields for date entries. Date information may be exposed through Decision Support Objects (DSO) and multidimensional expressions (MDX). These rely on the Year2000 compliance of the Microsoft Visual Basic® environment.

Processing queries and aggregations

Bounds checking and processing of queries and aggregations before, during, and after the rollover of January 1, 2000 have been verified and complete successfully.

Microsoft Repository:

 

Date storage

Repository accepts dates in the range January 1, 100 to December 31, 9999. It does not truncate the year to a 2-digit year so no reconversion is required at retrieval time. It stores the year in the form YYYY (in a DATE_STRUCT or TIMESTAMP_STRUCT structure, or the SQL Server datetime data type).

Formatting

Dates can be displayed in the format of MM/DD/YY, but this does not cause ambiguity because the dates are stored in SQL Server with 4-digit years.

Two digit shortcut handling

Applications must input dates using 4-digit years, attempting to input a 2-digit year results in an error. Engine-generated dates specify 4-digit years.

 

Microsoft Search Service:

The Microsoft Search Service that ships with SQL Server 7.0 works with data in character columns and has no dependencies on date data.

Testing guidelines and recommendations:

      • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to the datetime data type.
      • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
      • Investigate front-end application behavior using SQL Server as a backend and interaction with other applications.
      • SQL Server 7.0 supports a trace flag 8816 that records the 2-digit to 4-digit conversions done by the database engine. You can use this trace flag to determine if applications are sending SQL Server 2-digit years.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  7.0   (German)

Product Summary
Product: SQL Server Version: 7.0 Category:Compliant
Language: German OS: Win NT Release Date: 01 Nov 1998
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 11 Nov 1999
Product Details

This information applies to the Standard, Enterprise, Developer, Small Business, and Evaluation editions of SQL Server 7.0.

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 SQL Server 7.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.

 

Recommendations to meet compliance

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 7.0 installs Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, Microsoft recommends installing MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

How the product handles dates:

1) Server:

SQL Server has two date/time data types: datetime and smalldatetime. The datetime data type is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes are for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, through December 31, 9999, to an accuracy of one three-hundredth of a second (3.33 milliseconds).

Smalldatetime is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either data type allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. The "two-digit year cutoff" configuration option defines how SQL Server 7.0 expands a 2-digit year to four digits. The option is specified as a 4-digit year, the default is 2049. If only two digits are specified for a year, and they are less than or equal to the last two digits of the 2-digit year cutoff option, the date is stored as being in the same century as the option. If the specified two digits are greater than the last two digits of the 2-digit year cutoff option, the date is stored as being in the century before the one specified in the option. For example, if the 2-digit year cutoff option is left at its default of 2049, the value 49 is stored as 2049 and 50 is stored as 1950. If the 2-digit year cutoff option is set to 2029, the value 29 is stored as 2029 and 30 is stored as 1930. Earlier versions of SQL Server do not have a configurable 2-digit year cutoff option; they operate using a cutoff of 2049.

2) SQL Administration Tools:

SQL Server administration tools include SQL Server Enterprise Manager, SQL Server Profiler, SQL Server Query Analyzer, SQL Server Service Manager, Client Network Utility, Server Network Utility, SQL Server Agent, and more than 25 wizards. Several of these tools allow display and/or input of date information.

Date display:

Uses either SQL Server Engine formatting or Microsoft Windows NT® Control Panel settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the server include Transact-SQL, SQL Server Distributed Management Framework objects, OLE DB Provider for SQL Server, SQL Server ODBC driver, DB-Library, and Net-Libraries. Plausibility validation of entered dates happens mostly at the Microsoft Data Engine level for datetime and smalldatetime data types. SQL Server Agent, the job and alert scheduling engine of SQL Server, represents an exception: date information for scheduled jobs is stored in integer data types. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using the SQL Server ISDATE() function within stored procedures prior to storage in the database.

3) SQL Data Management Objects

Some SQL Data Management Objects have properties that represent dates. These properties are implemented as long integers in which dates are represented by numbers having the pattern YYYYMMDD. For example, the date April 19, 1998 is represented by the number 19980419.

4) Data Transformation Services

Data Transformation Services (DTS) supports transformations that map source string columns (DBTYPE_STR or DBTYPE_WSTR) to destination date columns (DBTYPE_DATE). The date portion of the strings in the source columns must be in the OLE DB format of YYYY-MM-DD. Transformations can also map source date columns to destination string columns, in which case the date portion is converted to a string having the OLE DB format of YYYY-MM-DD. For example, the OLE DB format for April 19, 1998 is 1998-04-19. Transformations using scripts, such as Microsoft ActiveX® or Microsoft Visual Basic® scripts, can also use the CDate() function for inputting dates.

5) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for 2-digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The default cutoff date observed by SQL Server 7.0 is 49, this maintains compatibility with earlier versions of SQL Server. If you are not concerned with compatibility with earlier versions of SQL Server, you can configure SQL Server to also use 29 as the cutoff date. For more information, see the SQL Server 7.0 Books Online.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying 2-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support 4-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

How the applications and components shipped with SQL Server 7.0 handle dates:

 

Microsoft English Query:

Date storage

Microsoft English Query does not store dates.

SQL generation

Date constants in generated SQL conditions use the generic date format YYYYMMDD. Year constants generated in SQL conditions use the format YYYY or YY, depending on a developer-controlled English Query setting on each year field. For fields marked to use the YY format, the century digits are simply omitted from the SQL condition.

Formatting

Dates in the testing tool are displayed using the ODBC text date format, which defaults to YYYY-MM-DD. ODBC can be configured to use regional settings instead.

Parsing on date entry

Dates can be input in questions using standard United States textual date formats. These include, but are not limited to:

    • Slash-formatted dates: (M)M/(D)D/(YY)YY
    • Text full dates: Month (D)D, (YY)YY
    • Text months: Month (YY)YY
    • Slash-formatted months: (M)M/(YY)YY

Two-digit shortcut handling

Microsoft English Query interprets years entered with a 2-digit shortcut as:

    • 1/1/00 through 12/31/29 is interpreted as 1/1/2000 through 12/31/2029.
    • 1/1/30 through 12/31/99 is interpreted as 1/1/1930 through 12/31/1999.

Microsoft OLAP Services:

 Date storage

Microsoft OLAP Services stores dates internally in the OLAP Services repository in accordance with the OLE DB for OLAP specification.

Formatting

The OLAP Services user interface does not include fields for date entries. Date information may be exposed through Decision Support Objects (DSO) and multidimensional expressions (MDX). These rely on the Year2000 compliance of the Microsoft Visual Basic® environment.

Processing queries and aggregations

Bounds checking and processing of queries and aggregations before, during, and after the rollover of January 1, 2000 have been verified and complete successfully.

Microsoft Repository:

 

Date storage

Repository accepts dates in the range January 1, 100 to December 31, 9999. It does not truncate the year to a 2-digit year so no reconversion is required at retrieval time. It stores the year in the form YYYY (in a DATE_STRUCT or TIMESTAMP_STRUCT structure, or the SQL Server datetime data type).

Formatting

Dates can be displayed in the format of MM/DD/YY, but this does not cause ambiguity because the dates are stored in SQL Server with 4-digit years.

Two digit shortcut handling

Applications must input dates using 4-digit years, attempting to input a 2-digit year results in an error. Engine-generated dates specify 4-digit years.

 

Microsoft Search Service:

The Microsoft Search Service that ships with SQL Server 7.0 works with data in character columns and has no dependencies on date data.

Testing guidelines and recommendations:

      • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to the datetime data type.
      • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
      • Investigate front-end application behavior using SQL Server as a backend and interaction with other applications.
      • SQL Server 7.0 supports a trace flag 8816 that records the 2-digit to 4-digit conversions done by the database engine. You can use this trace flag to determine if applications are sending SQL Server 2-digit years.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  7.0   (Japanese)

Product Summary
Product: SQL Server Version: 7.0 Category:Compliant
Language: Japanese OS: Win NT Release Date: 01 Nov 1998
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 11 Nov 1999
Product Details

This information applies to the Standard, Enterprise, Developer, Small Business, and Evaluation editions of SQL Server 7.0.

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 SQL Server 7.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.

 

Recommendations to meet compliance

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 7.0 installs Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, Microsoft recommends installing MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

How the product handles dates:

1) Server:

SQL Server has two date/time data types: datetime and smalldatetime. The datetime data type is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes are for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, through December 31, 9999, to an accuracy of one three-hundredth of a second (3.33 milliseconds).

Smalldatetime is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either data type allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. The "two-digit year cutoff" configuration option defines how SQL Server 7.0 expands a 2-digit year to four digits. The option is specified as a 4-digit year, the default is 2049. If only two digits are specified for a year, and they are less than or equal to the last two digits of the 2-digit year cutoff option, the date is stored as being in the same century as the option. If the specified two digits are greater than the last two digits of the 2-digit year cutoff option, the date is stored as being in the century before the one specified in the option. For example, if the 2-digit year cutoff option is left at its default of 2049, the value 49 is stored as 2049 and 50 is stored as 1950. If the 2-digit year cutoff option is set to 2029, the value 29 is stored as 2029 and 30 is stored as 1930. Earlier versions of SQL Server do not have a configurable 2-digit year cutoff option; they operate using a cutoff of 2049.

2) SQL Administration Tools:

SQL Server administration tools include SQL Server Enterprise Manager, SQL Server Profiler, SQL Server Query Analyzer, SQL Server Service Manager, Client Network Utility, Server Network Utility, SQL Server Agent, and more than 25 wizards. Several of these tools allow display and/or input of date information.

Date display:

Uses either SQL Server Engine formatting or Microsoft Windows NT® Control Panel settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the server include Transact-SQL, SQL Server Distributed Management Framework objects, OLE DB Provider for SQL Server, SQL Server ODBC driver, DB-Library, and Net-Libraries. Plausibility validation of entered dates happens mostly at the Microsoft Data Engine level for datetime and smalldatetime data types. SQL Server Agent, the job and alert scheduling engine of SQL Server, represents an exception: date information for scheduled jobs is stored in integer data types. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using the SQL Server ISDATE() function within stored procedures prior to storage in the database.

3) SQL Data Management Objects

Some SQL Data Management Objects have properties that represent dates. These properties are implemented as long integers in which dates are represented by numbers having the pattern YYYYMMDD. For example, the date April 19, 1998 is represented by the number 19980419.

4) Data Transformation Services

Data Transformation Services (DTS) supports transformations that map source string columns (DBTYPE_STR or DBTYPE_WSTR) to destination date columns (DBTYPE_DATE). The date portion of the strings in the source columns must be in the OLE DB format of YYYY-MM-DD. Transformations can also map source date columns to destination string columns, in which case the date portion is converted to a string having the OLE DB format of YYYY-MM-DD. For example, the OLE DB format for April 19, 1998 is 1998-04-19. Transformations using scripts, such as Microsoft ActiveX® or Microsoft Visual Basic® scripts, can also use the CDate() function for inputting dates.

5) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for 2-digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The default cutoff date observed by SQL Server 7.0 is 49, this maintains compatibility with earlier versions of SQL Server. If you are not concerned with compatibility with earlier versions of SQL Server, you can configure SQL Server to also use 29 as the cutoff date. For more information, see the SQL Server 7.0 Books Online.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying 2-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support 4-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

How the applications and components shipped with SQL Server 7.0 handle dates:

 

Microsoft English Query:

Date storage

Microsoft English Query does not store dates.

SQL generation

Date constants in generated SQL conditions use the generic date format YYYYMMDD. Year constants generated in SQL conditions use the format YYYY or YY, depending on a developer-controlled English Query setting on each year field. For fields marked to use the YY format, the century digits are simply omitted from the SQL condition.

Formatting

Dates in the testing tool are displayed using the ODBC text date format, which defaults to YYYY-MM-DD. ODBC can be configured to use regional settings instead.

Parsing on date entry

Dates can be input in questions using standard United States textual date formats. These include, but are not limited to:

    • Slash-formatted dates: (M)M/(D)D/(YY)YY
    • Text full dates: Month (D)D, (YY)YY
    • Text months: Month (YY)YY
    • Slash-formatted months: (M)M/(YY)YY

Two-digit shortcut handling

Microsoft English Query interprets years entered with a 2-digit shortcut as:

    • 1/1/00 through 12/31/29 is interpreted as 1/1/2000 through 12/31/2029.
    • 1/1/30 through 12/31/99 is interpreted as 1/1/1930 through 12/31/1999.

Microsoft OLAP Services:

 Date storage

Microsoft OLAP Services stores dates internally in the OLAP Services repository in accordance with the OLE DB for OLAP specification.

Formatting

The OLAP Services user interface does not include fields for date entries. Date information may be exposed through Decision Support Objects (DSO) and multidimensional expressions (MDX). These rely on the Year2000 compliance of the Microsoft Visual Basic® environment.

Processing queries and aggregations

Bounds checking and processing of queries and aggregations before, during, and after the rollover of January 1, 2000 have been verified and complete successfully.

Microsoft Repository:

 

Date storage

Repository accepts dates in the range January 1, 100 to December 31, 9999. It does not truncate the year to a 2-digit year so no reconversion is required at retrieval time. It stores the year in the form YYYY (in a DATE_STRUCT or TIMESTAMP_STRUCT structure, or the SQL Server datetime data type).

Formatting

Dates can be displayed in the format of MM/DD/YY, but this does not cause ambiguity because the dates are stored in SQL Server with 4-digit years.

Two digit shortcut handling

Applications must input dates using 4-digit years, attempting to input a 2-digit year results in an error. Engine-generated dates specify 4-digit years.

 

Microsoft Search Service:

The Microsoft Search Service that ships with SQL Server 7.0 works with data in character columns and has no dependencies on date data.

Testing guidelines and recommendations:

      • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to the datetime data type.
      • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
      • Investigate front-end application behavior using SQL Server as a backend and interaction with other applications.
      • SQL Server 7.0 supports a trace flag 8816 that records the 2-digit to 4-digit conversions done by the database engine. You can use this trace flag to determine if applications are sending SQL Server 2-digit years.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
SQL Server  7.0   (Spanish)

Product Summary
Product: SQL Server Version: 7.0 Category:Compliant
Language: Spanish OS: Win NT Release Date: 01 Nov 1998
Operational Range: 01 Jan 1753 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Microsoft Data Access Components (MDAC), DCOM95, Internet Explorer 4.0, OLE Automation Technology, Server and Client platforms documented in SQL Server System requirements.
Clock Dependencies: System Clock
Last Updated: 11 Nov 1999
Product Details

This information applies to the Standard, Enterprise, Developer, Small Business, and Evaluation editions of SQL Server 7.0.

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 SQL Server 7.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.

 

Recommendations to meet compliance

Ensure that all the dependent products listed above are compliant on the computer running SQL Server software. Review the Year 2000 documentation for the dependent products to find out what versions or service packs must be installed to make the dependent products Year 2000 compliant.

SQL Server 7.0 installs Microsoft Data Access Components (MDAC) 2.1. MDAC 2.1 now has a software update for a Jet engine issue. While SQL Server does not expose the issue, Microsoft recommends installing MDAC 2.1 Service Pack 1 or later should this be a concern for you. For more information, see the Year 2000 document for the Jet Database Engine.

How the product handles dates:

1) Server:

SQL Server has two date/time data types: datetime and smalldatetime. The datetime data type is stored in 8 bytes of two 4-byte integers. The first 4 bytes are for the number of days before or after the base date of January 1, 1900, and the other 4 bytes are for the number of milliseconds after midnight. The values for datetime range from January 1, 1753, through December 31, 9999, to an accuracy of one three-hundredth of a second (3.33 milliseconds).

Smalldatetime is less precise than datetime, and is stored in 4 bytes consisting of one small integer for the number of days after January 1, 1900, and one small integer for the number of minutes past midnight. The values for smalldatetime range from January 1, 1900, through June 6, 2079, with accuracy to the minute.

Either data type allows users to specify only the last 2 digits of the year. However the year is still stored the same as if 4 digits were specified. The "two-digit year cutoff" configuration option defines how SQL Server 7.0 expands a 2-digit year to four digits. The option is specified as a 4-digit year, the default is 2049. If only two digits are specified for a year, and they are less than or equal to the last two digits of the 2-digit year cutoff option, the date is stored as being in the same century as the option. If the specified two digits are greater than the last two digits of the 2-digit year cutoff option, the date is stored as being in the century before the one specified in the option. For example, if the 2-digit year cutoff option is left at its default of 2049, the value 49 is stored as 2049 and 50 is stored as 1950. If the 2-digit year cutoff option is set to 2029, the value 29 is stored as 2029 and 30 is stored as 1930. Earlier versions of SQL Server do not have a configurable 2-digit year cutoff option; they operate using a cutoff of 2049.

2) SQL Administration Tools:

SQL Server administration tools include SQL Server Enterprise Manager, SQL Server Profiler, SQL Server Query Analyzer, SQL Server Service Manager, Client Network Utility, Server Network Utility, SQL Server Agent, and more than 25 wizards. Several of these tools allow display and/or input of date information.

Date display:

Uses either SQL Server Engine formatting or Microsoft Windows NT® Control Panel settings formatting.

Date input:

Dates are achieved using either Edit fields or Date controls. Transport means for date information to the server include Transact-SQL, SQL Server Distributed Management Framework objects, OLE DB Provider for SQL Server, SQL Server ODBC driver, DB-Library, and Net-Libraries. Plausibility validation of entered dates happens mostly at the Microsoft Data Engine level for datetime and smalldatetime data types. SQL Server Agent, the job and alert scheduling engine of SQL Server, represents an exception: date information for scheduled jobs is stored in integer data types. Plausibility of entered dates in this case is evaluated within the user interface Date controls and by using the SQL Server ISDATE() function within stored procedures prior to storage in the database.

3) SQL Data Management Objects

Some SQL Data Management Objects have properties that represent dates. These properties are implemented as long integers in which dates are represented by numbers having the pattern YYYYMMDD. For example, the date April 19, 1998 is represented by the number 19980419.

4) Data Transformation Services

Data Transformation Services (DTS) supports transformations that map source string columns (DBTYPE_STR or DBTYPE_WSTR) to destination date columns (DBTYPE_DATE). The date portion of the strings in the source columns must be in the OLE DB format of YYYY-MM-DD. Transformations can also map source date columns to destination string columns, in which case the date portion is converted to a string having the OLE DB format of YYYY-MM-DD. For example, the OLE DB format for April 19, 1998 is 1998-04-19. Transformations using scripts, such as Microsoft ActiveX® or Microsoft Visual Basic® scripts, can also use the CDate() function for inputting dates.

5) Application Programming

General purpose SQL Server applications use the Transact-SQL language to work with the data in SQL Server databases. The Transact-SQL language is processed on the server, and dates in Transact-SQL statements are handled using the rules specified above in 1) Server. SQL Server applications use one of several application programming interfaces (APIs) to send Transact-SQL statements to the server and process the results. Dates can be specified either as part of the Transact-SQL statement sent to SQL Server, or in program variables bound to Transact-SQL parameters or expressions through the API. If dates are specified as a part of a Transact-SQL statement, they are handled on the server using the rules specified in the 1) Server section. Dates specified in variables bound to parameters and expressions through the API are subject to the rules for the API:

OLE DB (using the Microsoft OLE DB Provider for SQL Server):

Dates can be specified using the OLE DB API. For these dates, the Microsoft OLE DB Provider for SQL Server is subject to the same date coercion rules that apply to OLE DB. For more information, see the Year 2000 documentation for the MS Data Access Components (MDAC). The Microsoft OLE DB Provider is also subject to the date conversion rules that apply to the OLE Automation Technologies. For more information, see the Year 2000 document for OLE Automation Technologies.

The OLE DB cutoff date for 2-digit year conversions defaults to 29, dates that are less than or equal to 29 are interpreted as 20xx and dates that are greater than 29 are interpreted as 19xx. For information on configuring the cutoff date, see the Year 2000 document for OLE Automation Technologies. The default cutoff date observed by SQL Server 7.0 is 49, this maintains compatibility with earlier versions of SQL Server. If you are not concerned with compatibility with earlier versions of SQL Server, you can configure SQL Server to also use 29 as the cutoff date. For more information, see the SQL Server 7.0 Books Online.

ODBC (Using the SQL Server ODBC Driver):

The ODBC API does not support specifying 2-digit years, it only supports specifying four-digit years. ODBC recommends that applications use ODBC timestamp escape sequences to specify dates in SQL statements, and the timestamp escape sequences only support 4-digit years. The SQL Server ODBC Driver, however, does not prevent users from entering Transact-SQL dates. If Transact-SQL dates are used, they are handled on the server using the rules specified in the 1) Server section.

DB-Library:

The DB-Library does not provide any means for specifying dates other than specifying them as part of Transact-SQL statements. These dates are handled on the server using the rules specified in the 1) Server section.

How the applications and components shipped with SQL Server 7.0 handle dates:

 

Microsoft English Query:

Date storage

Microsoft English Query does not store dates.

SQL generation

Date constants in generated SQL conditions use the generic date format YYYYMMDD. Year constants generated in SQL conditions use the format YYYY or YY, depending on a developer-controlled English Query setting on each year field. For fields marked to use the YY format, the century digits are simply omitted from the SQL condition.

Formatting

Dates in the testing tool are displayed using the ODBC text date format, which defaults to YYYY-MM-DD. ODBC can be configured to use regional settings instead.

Parsing on date entry

Dates can be input in questions using standard United States textual date formats. These include, but are not limited to:

    • Slash-formatted dates: (M)M/(D)D/(YY)YY
    • Text full dates: Month (D)D, (YY)YY
    • Text months: Month (YY)YY
    • Slash-formatted months: (M)M/(YY)YY

Two-digit shortcut handling

Microsoft English Query interprets years entered with a 2-digit shortcut as:

    • 1/1/00 through 12/31/29 is interpreted as 1/1/2000 through 12/31/2029.
    • 1/1/30 through 12/31/99 is interpreted as 1/1/1930 through 12/31/1999.

Microsoft OLAP Services:

 Date storage

Microsoft OLAP Services stores dates internally in the OLAP Services repository in accordance with the OLE DB for OLAP specification.

Formatting

The OLAP Services user interface does not include fields for date entries. Date information may be exposed through Decision Support Objects (DSO) and multidimensional expressions (MDX). These rely on the Year2000 compliance of the Microsoft Visual Basic® environment.

Processing queries and aggregations

Bounds checking and processing of queries and aggregations before, during, and after the rollover of January 1, 2000 have been verified and complete successfully.

Microsoft Repository:

 

Date storage

Repository accepts dates in the range January 1, 100 to December 31, 9999. It does not truncate the year to a 2-digit year so no reconversion is required at retrieval time. It stores the year in the form YYYY (in a DATE_STRUCT or TIMESTAMP_STRUCT structure, or the SQL Server datetime data type).

Formatting

Dates can be displayed in the format of MM/DD/YY, but this does not cause ambiguity because the dates are stored in SQL Server with 4-digit years.

Two digit shortcut handling

Applications must input dates using 4-digit years, attempting to input a 2-digit year results in an error. Engine-generated dates specify 4-digit years.

 

Microsoft Search Service:

The Microsoft Search Service that ships with SQL Server 7.0 works with data in character columns and has no dependencies on date data.

Testing guidelines and recommendations:

      • Examine the database schema to see whether smalldatetime datatypes are used; in some cases, in order to achieve higher precision, it is recommended to convert these to the datetime data type.
      • Use 4-digit year input to avoid ambiguities or boundary conditions in applications.
      • Investigate front-end application behavior using SQL Server as a backend and interaction with other applications.
      • SQL Server 7.0 supports a trace flag 8816 that records the 2-digit to 4-digit conversions done by the database engine. You can use this trace flag to determine if applications are sending SQL Server 2-digit years.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
Stravinsky  1.0   (English)

Product Summary
Product: Stravinsky Version: 1.0 Category:Compliant
Language: English OS: 16-Bit Win Release Date: 01 Mar 1993
Operational Range: -
Prerequisites: NONE
Product Dependencies: DOS or Win 3.1
Clock Dependencies: System Clock
Last Updated: 02 Nov 1999
Product Details

 

How the product handles dates:

No date handling or two-digit shortcut interpretation is performed.

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
System Mgmt Server  1.2   (Chinese - Simplified)

Product Summary
Product: System Mgmt Server Version: 1.2 Category:Compliant*
Language: Chinese - Simplified OS: Win NT Release Date: 13 Sep 1996
Operational Range: 01 Jan 1980 - 31 Dec 2035
Prerequisites: Systems Management Server 1.2 Service Pack 4
Product Dependencies: Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5
Clock Dependencies: System Clock
Last Updated: 21 Oct 1999
Product Details

 

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 Systems Management Server 1.2 Service Pack 4 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.

Systems Management Server 1.2 through Service Pack 3 is Compliant#.

The acceptable deviation:

When trying to inventory software users are unable to create a query with the user interface for files with a date stamp in the year 2000. Note: Any date prior to 1/1/2000 or after 12/31/2000 works properly. This issue can be worked around by importing a Package Definition File (PDF) which already contains an inventory rule rather than creating the rule in the user interface. Service Pack 4 resolves this issue.

Microsoft Systems Management Server version 1.2 Service Pack 4 is a prerequisite and is assumed for the information described below.

Systems Management Server 1.2 Service Pack 4 is available from:

ftp://ftp.microsoft.com/Softlib/MSLFILES/SMS12SP4.EXE

Service pack 4 fixes known issues with Systems Management Server 1.2 as indicated by the information below. Microsoft SMS 1.2 can use earlier versions of SQL Server, however SMS is dependent on SQL 6.5 for its Year 2000 test information. The Systems Management Server Installer, freely available as a web download for all version 1.2 customers, is also compliant from version 2.0.64 onwards. The current version at http://www.microsoft.com/smsmgmt/downloads/install.asp

is compliant and older versions can be seamlessly upgraded to this version as needed.

Systems Management Server Architecture

Subsystem

Component

Microsoft's Testing Summary

Sites

Personal Computer Properties

Workstation Status

- Last Hardware scan

- Last Software scan

For both Last HW and SW scan

Before Year 2000 - Works properly

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" HW and SW scan for the respective client will not get updated properly on the server until the client's clock is past the Last HW and SW scan already represented on the server. Resetting the client’s clock to the correct time solves this problem until the next century.

 

Operating System

- Install Date

Operating Systems installed before the Year 2000 are represented properly in the SMS Admin User Interface before and after the Year 2000.

Operating Systems installed after the Year 2000 are represented correctly.

Operating Systems installed on 2/29/2000 are represented correctly

 

File

Properties

Site Properties

- Last report GMT

- Last report Local

Before Year 2000 - Works properly.

Site servers whose BIOS clocks rollover from 1999 to 2000, works properly.

Site servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" report GMT and Local will not get updated until the server's clock is ahead of the Last report GMT and Local already represented on the server. Resetting the server's clock to the correct time solves this problem.

 

Inventory

Hardware Inventory Frequency

- Every N Days

Software Inventory Frequency

- Every N Days

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, inventory will not occur until the client's clock is at the last HW or SW inventory + N days. This functionality is all on the client in the SMS.INI. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, updating the inventory frequency functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the update of the site properties will not occur until the site's date is past the last time the site control file was updated before the BIOS rollover error. Resetting the server's clock to the correct time solves this problem.

 

Clients

PCM Polling Interval,

- Every N Minutes

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover properly from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the interval works properly but offers from the server are slated to begin after a certain date. The client's clock is well in the past and therefore offers will not appear in the client's PCM User Interface. Resetting the clients' clock to the correct time solves this problem.

 

Account

Service account

- Last Valid Password Created

Represented properly.

If the site server's clock rolls-over to 1980 the account will not expire for an extra 20 Years and changing it through the SMS Admin User Interface is not possible until the systems date is past the last update for the site control file.

 

Outbox

- Schedule

If the server's BIOS clock works properly:

1999 rolling over to 2000 works properly.

2/29/2000 poses no problems.


If the server's BIOS clock does not rollover to the Year 2000, but reverts to 1980, whichever day of the week in 1980 the clock reverts to, and subsequent days, is the schedule the Outbox Schedule will follow. Regardless of this, the mechanism, which initiates the sending of information from this site server will not launch, because it views this as an "old" request to send.

 

Execute Queries

- Query results (Header bar)

Dates before Year 2000 - Works properly

Dates after Year 2000 -Works properly

 

Execute query with the following

- is

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is not

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is on or after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- is on or before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Define Query result Formats

Properties ( Identification)

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Machines with last activity

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are listed in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Jobs

File

"Jobs" Window

Dates are listed properly and sorted in correct chronological order.

 

New

Run Command on Workstation

Details

Send Phase

- Only if Not previously

sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Even if Previously Sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Run Workstation Command

- Offer after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clock rolls-over from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not occur until the site's date and time matches that for the job.

 

- Mandatory after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs become mandatory properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the mandatory job is launched.

Regarding Servers

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, this has no effect on the clients except the offer after and job schedule dates will prevent jobs from being launched or reaching the clients.

 

- Expires after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs expire properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not expire until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the job expires.

Regarding Servers

Before Year 2000 – Works properly.

Servers whose BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, job will not truly expire until the expiration date is reached on the server.

 

Job Schedule

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the job will not go active until the scheduled date.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, the old jobs now happen in the future

 

View

- All details

Dates are listed in correct chronological order.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Packages

File

Properties

Inventory

- Package Properties

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Alerts

New

- Alert query

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Events

File

Properties

Event Detail

- Time:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the old events now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SNMP Traps

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the traps now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SQL Server Messages

Event Display

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Database

Manager

Edit

Merge History For Selected PCs

Works properly.

 

Machines

Duplicate machines

- Last hardware scan

Regarding Clients

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, performs properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000, the last hardware scan is time stamped with the same time stamp of the first hardware scan. Resetting the client's clock to the correct time solves this problem for the next hardware scans.

Regarding Servers

Before Year 2000 - Works properly.

For servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

For servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, this has no effect.

 

Tools

Delete Collected files

Select by date

Select Cut-Off Date

- No Activity Since: (m/d/y)

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, it is the clients’ clock which time stamps this.

 

- Select by number of inactive

days

- Minimum inactive days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, does not function properly. Resetting the system clock solves this.

Package Control Manager

Log File

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, perform properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000 accurately report the inaccurate date(s).

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
System Mgmt Server  1.2   (Chinese - Traditional)

Product Summary
Product: System Mgmt Server Version: 1.2 Category:Compliant*
Language: Chinese - Traditional OS: Win NT Release Date: 13 Sep 1996
Operational Range: 01 Jan 1980 - 31 Dec 2035
Prerequisites: Systems Management Server 1.2 Service Pack 4
Product Dependencies: Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5
Clock Dependencies: System Clock
Last Updated: 21 Oct 1999
Product Details

 

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 Systems Management Server 1.2 Service Pack 4 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.

Systems Management Server 1.2 through Service Pack 3 is Compliant#.

The acceptable deviation:

When trying to inventory software users are unable to create a query with the user interface for files with a date stamp in the year 2000. Note: Any date prior to 1/1/2000 or after 12/31/2000 works properly. This issue can be worked around by importing a Package Definition File (PDF) which already contains an inventory rule rather than creating the rule in the user interface. Service Pack 4 resolves this issue.

Microsoft Systems Management Server version 1.2 Service Pack 4 is a prerequisite and is assumed for the information described below.

Systems Management Server 1.2 Service Pack 4 is available from:

ftp://ftp.microsoft.com/Softlib/MSLFILES/SMS12SP4.EXE

Service pack 4 fixes known issues with Systems Management Server 1.2 as indicated by the information below. Microsoft SMS 1.2 can use earlier versions of SQL Server, however SMS is dependent on SQL 6.5 for its Year 2000 test information. The Systems Management Server Installer, freely available as a web download for all version 1.2 customers, is also compliant from version 2.0.64 onwards. The current version at http://www.microsoft.com/smsmgmt/downloads/install.asp

is compliant and older versions can be seamlessly upgraded to this version as needed.

Systems Management Server Architecture

Subsystem

Component

Microsoft's Testing Summary

Sites

Personal Computer Properties

Workstation Status

- Last Hardware scan

- Last Software scan

For both Last HW and SW scan

Before Year 2000 - Works properly

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" HW and SW scan for the respective client will not get updated properly on the server until the client's clock is past the Last HW and SW scan already represented on the server. Resetting the client’s clock to the correct time solves this problem until the next century.

 

Operating System

- Install Date

Operating Systems installed before the Year 2000 are represented properly in the SMS Admin User Interface before and after the Year 2000.

Operating Systems installed after the Year 2000 are represented correctly.

Operating Systems installed on 2/29/2000 are represented correctly

 

File

Properties

Site Properties

- Last report GMT

- Last report Local

Before Year 2000 - Works properly.

Site servers whose BIOS clocks rollover from 1999 to 2000, works properly.

Site servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" report GMT and Local will not get updated until the server's clock is ahead of the Last report GMT and Local already represented on the server. Resetting the server's clock to the correct time solves this problem.

 

Inventory

Hardware Inventory Frequency

- Every N Days

Software Inventory Frequency

- Every N Days

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, inventory will not occur until the client's clock is at the last HW or SW inventory + N days. This functionality is all on the client in the SMS.INI. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, updating the inventory frequency functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the update of the site properties will not occur until the site's date is past the last time the site control file was updated before the BIOS rollover error. Resetting the server's clock to the correct time solves this problem.

 

Clients

PCM Polling Interval,

- Every N Minutes

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover properly from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the interval works properly but offers from the server are slated to begin after a certain date. The client's clock is well in the past and therefore offers will not appear in the client's PCM User Interface. Resetting the clients' clock to the correct time solves this problem.

 

Account

Service account

- Last Valid Password Created

Represented properly.

If the site server's clock rolls-over to 1980 the account will not expire for an extra 20 Years and changing it through the SMS Admin User Interface is not possible until the systems date is past the last update for the site control file.

 

Outbox

- Schedule

If the server's BIOS clock works properly:

1999 rolling over to 2000 works properly.

2/29/2000 poses no problems.


If the server's BIOS clock does not rollover to the Year 2000, but reverts to 1980, whichever day of the week in 1980 the clock reverts to, and subsequent days, is the schedule the Outbox Schedule will follow. Regardless of this, the mechanism, which initiates the sending of information from this site server will not launch, because it views this as an "old" request to send.

 

Execute Queries

- Query results (Header bar)

Dates before Year 2000 - Works properly

Dates after Year 2000 -Works properly

 

Execute query with the following

- is

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is not

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is on or after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- is on or before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Define Query result Formats

Properties ( Identification)

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Machines with last activity

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are listed in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Jobs

File

"Jobs" Window

Dates are listed properly and sorted in correct chronological order.

 

New

Run Command on Workstation

Details

Send Phase

- Only if Not previously

sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Even if Previously Sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Run Workstation Command

- Offer after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clock rolls-over from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not occur until the site's date and time matches that for the job.

 

- Mandatory after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs become mandatory properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the mandatory job is launched.

Regarding Servers

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, this has no effect on the clients except the offer after and job schedule dates will prevent jobs from being launched or reaching the clients.

 

- Expires after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs expire properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not expire until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the job expires.

Regarding Servers

Before Year 2000 – Works properly.

Servers whose BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, job will not truly expire until the expiration date is reached on the server.

 

Job Schedule

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the job will not go active until the scheduled date.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, the old jobs now happen in the future

 

View

- All details

Dates are listed in correct chronological order.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Packages

File

Properties

Inventory

- Package Properties

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Alerts

New

- Alert query

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Events

File

Properties

Event Detail

- Time:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the old events now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SNMP Traps

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the traps now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SQL Server Messages

Event Display

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Database

Manager

Edit

Merge History For Selected PCs

Works properly.

 

Machines

Duplicate machines

- Last hardware scan

Regarding Clients

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, performs properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000, the last hardware scan is time stamped with the same time stamp of the first hardware scan. Resetting the client's clock to the correct time solves this problem for the next hardware scans.

Regarding Servers

Before Year 2000 - Works properly.

For servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

For servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, this has no effect.

 

Tools

Delete Collected files

Select by date

Select Cut-Off Date

- No Activity Since: (m/d/y)

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, it is the clients’ clock which time stamps this.

 

- Select by number of inactive

days

- Minimum inactive days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, does not function properly. Resetting the system clock solves this.

Package Control Manager

Log File

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, perform properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000 accurately report the inaccurate date(s).

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Microsoft Year 2000 Resource Center
System Mgmt Server  1.2   (Danish)

Product Summary
Product: System Mgmt Server Version: 1.2 Category:Compliant*
Language: Danish OS: Win NT Release Date: 13 Sep 1996
Operational Range: 01 Jan 1980 - 31 Dec 2053
Prerequisites: Systems Management Server 1.2 Service Pack 4
Product Dependencies: Windows NT Server 3.51 (Service Pack 3) or later or Windows NT Server 4.0, Microsoft SQL Server 6.5
Clock Dependencies: System Clock
Last Updated: 21 Oct 1999
Product Details

 

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 Systems Management Server 1.2 Service Pack 4 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.

Systems Management Server 1.2 through Service Pack 3 is Compliant#.

The acceptable deviation:

When trying to inventory software users are unable to create a query with the user interface for files with a date stamp in the year 2000. Note: Any date prior to 1/1/2000 or after 12/31/2000 works properly. This issue can be worked around by importing a Package Definition File (PDF) which already contains an inventory rule rather than creating the rule in the user interface. Service Pack 4 resolves this issue.

Microsoft Systems Management Server version 1.2 Service Pack 4 is a prerequisite and is assumed for the information described below.

Systems Management Server 1.2 Service Pack 4 is available from:

ftp://ftp.microsoft.com/Softlib/MSLFILES/SMS12SP4.EXE

Service pack 4 fixes known issues with Systems Management Server 1.2 as indicated by the information below. Microsoft SMS 1.2 can use earlier versions of SQL Server, however SMS is dependent on SQL 6.5 for its Year 2000 test information. The Systems Management Server Installer, freely available as a web download for all version 1.2 customers, is also compliant from version 2.0.64 onwards. The current version at http://www.microsoft.com/smsmgmt/downloads/install.asp

is compliant and older versions can be seamlessly upgraded to this version as needed.

Systems Management Server Architecture

Subsystem

Component

Microsoft's Testing Summary

Sites

Personal Computer Properties

Workstation Status

- Last Hardware scan

- Last Software scan

For both Last HW and SW scan

Before Year 2000 - Works properly

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" HW and SW scan for the respective client will not get updated properly on the server until the client's clock is past the Last HW and SW scan already represented on the server. Resetting the client’s clock to the correct time solves this problem until the next century.

 

Operating System

- Install Date

Operating Systems installed before the Year 2000 are represented properly in the SMS Admin User Interface before and after the Year 2000.

Operating Systems installed after the Year 2000 are represented correctly.

Operating Systems installed on 2/29/2000 are represented correctly

 

File

Properties

Site Properties

- Last report GMT

- Last report Local

Before Year 2000 - Works properly.

Site servers whose BIOS clocks rollover from 1999 to 2000, works properly.

Site servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the "Last" report GMT and Local will not get updated until the server's clock is ahead of the Last report GMT and Local already represented on the server. Resetting the server's clock to the correct time solves this problem.

 

Inventory

Hardware Inventory Frequency

- Every N Days

Software Inventory Frequency

- Every N Days

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, inventory will not occur until the client's clock is at the last HW or SW inventory + N days. This functionality is all on the client in the SMS.INI. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, updating the inventory frequency functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the update of the site properties will not occur until the site's date is past the last time the site control file was updated before the BIOS rollover error. Resetting the server's clock to the correct time solves this problem.

 

Clients

PCM Polling Interval,

- Every N Minutes

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover properly from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the interval works properly but offers from the server are slated to begin after a certain date. The client's clock is well in the past and therefore offers will not appear in the client's PCM User Interface. Resetting the clients' clock to the correct time solves this problem.

 

Account

Service account

- Last Valid Password Created

Represented properly.

If the site server's clock rolls-over to 1980 the account will not expire for an extra 20 Years and changing it through the SMS Admin User Interface is not possible until the systems date is past the last update for the site control file.

 

Outbox

- Schedule

If the server's BIOS clock works properly:

1999 rolling over to 2000 works properly.

2/29/2000 poses no problems.


If the server's BIOS clock does not rollover to the Year 2000, but reverts to 1980, whichever day of the week in 1980 the clock reverts to, and subsequent days, is the schedule the Outbox Schedule will follow. Regardless of this, the mechanism, which initiates the sending of information from this site server will not launch, because it views this as an "old" request to send.

 

Execute Queries

- Query results (Header bar)

Dates before Year 2000 - Works properly

Dates after Year 2000 -Works properly

 

Execute query with the following

- is

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is not

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is on or after

Dates before Year 2000 - Works properly

Dates after Year 2000 - Works properly

 

- is before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- is on or before

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Define Query result Formats

Properties ( Identification)

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Machines with last activity

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are listed in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Jobs

File

"Jobs" Window

Dates are listed properly and sorted in correct chronological order.

 

New

Run Command on Workstation

Details

Send Phase

- Only if Not previously

sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Even if Previously Sent

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Run Workstation Command

- Offer after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clocks rollover from 1999 to 2000, works properly.

Clients whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem.

Regarding Servers

Before Year 2000 - Works properly.

Servers whose BIOS clock rolls-over from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the offer will not occur until the site's date and time matches that for the job.

 

- Mandatory after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs become mandatory properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not appear on the client until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the mandatory job is launched.

Regarding Servers

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, this has no effect on the clients except the offer after and job schedule dates will prevent jobs from being launched or reaching the clients.

 

- Expires after

Regarding Clients

Before Year 2000 - Works properly.

Clients whose BIOS clock rolls-over from 1999 to 2000, jobs expire properly.

Clients whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, the offer will not expire until the offer date for the job is reached by the client. Resetting the client's clock to the correct time solves this problem and the job expires.

Regarding Servers

Before Year 2000 – Works properly.

Servers whose BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the roll-over from 1999 to 2000, job will not truly expire until the expiration date is reached on the server.

 

Job Schedule

Before Year 2000 - Works properly.

Servers whose BIOS clocks rollover properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, the job will not go active until the scheduled date.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, the old jobs now happen in the future

 

View

- All details

Dates are listed in correct chronological order.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Packages

File

Properties

Inventory

- Package Properties

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Alerts

New

- Alert query

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Events

File

Properties

Event Detail

- Time:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the old events now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SNMP Traps

Edit

Delete Special

- Dated Before:

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Older Than: N Days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks reset to 1980 on the rollover from 1999 to 2000, the traps now happen in the future

 

View

- All details

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

 

- Sort

Dates are sorted in correct chronological order.

 

- Filter

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

SQL Server Messages

Event Display

Dates before Year 2000 - Works properly.

Dates after Year 2000 - Works properly.

Database

Manager

Edit

Merge History For Selected PCs

Works properly.

 

Machines

Duplicate machines

- Last hardware scan

Regarding Clients

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, performs properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000, the last hardware scan is time stamped with the same time stamp of the first hardware scan. Resetting the client's clock to the correct time solves this problem for the next hardware scans.

Regarding Servers

Before Year 2000 - Works properly.

For servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

For servers whose BIOS clocks' reset to 1980 on the rollover from 1999 to 2000, this has no effect.

 

Tools

Delete Collected files

Select by date

Select Cut-Off Date

- No Activity Since: (m/d/y)

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clock resets to 1980 on the rollover from 1999 to 2000, it is the clients’ clock which time stamps this.

 

- Select by number of inactive

days

- Minimum inactive days

Before Year 2000 - Works properly.

Servers where the BIOS clock rolls-over properly from 1999 to 2000, functions properly.

Servers whose BIOS clocks resets to 1980 on the rollover from 1999 to 2000, does not function properly. Resetting the system clock solves this.

Package Control Manager

Log File

Before Year 2000 - Works properly.

Clients where the BIOS clock rolls-over from 1999 to 2000, perform properly.

Clients where the BIOS clock resets to 1980 on the rollover from 1999 to 2000 accurately report the inaccurate date(s).

 


Legend of Symbols:
*The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#The product is compliant with an acceptable deviation from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability or reliability of the product.
+The product is compliant . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.


Itemized List of products in each Volume

YEAR 2000 READINESS DISCLOSURE

ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://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.