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
Access 97  8.0   (Korean)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98 or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://www.microsoft.com/korea/office/97/sr2.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Norwegian)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Polish)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Polish OS: 32-Bit Win Release Date: N/A
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm

The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Portuguese (Brazil))

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98 or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm

The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.

The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Portuguese)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Portuguese OS: 32-Bit Win Release Date: N/A
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Russian)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Slovak)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Slovak OS: 32-Bit Win Release Date: N/A
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Year 2000 Software Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 05 Oct 1999
Product Details

Prerequisites: To download the jet 3.5 update file see Knowledge Base article Q172733.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.
Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. Custom formats can be created to display years as 4-digits.
Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC:Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Spanish)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Swedish)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Thai)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*#
Language: Thai OS: 32-Bit Win Release Date: 21 Jul 1997
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Microsoft Jet 3.5 Update
Product Dependencies: Microsoft Thai Windows 95 or Thai Windows NT 4 (no specific SP is required)
Clock Dependencies: System clock
Last Updated: 29 Sep 1999
Product Details

Prerequisites:

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. The oleaut32.dll v2.20 that shipped with Thai Access97 only supports parsing dates entered in the m/d/yy format regardless of the regional setting. If the year is greater than 2266 then date is assumed to be a Buddhist year. If the year is less than or equal to 2266 then date is assumed to be a Gregorian year. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC:Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access 97  8.0   (Turkish)

Product Summary
Product: Access 97 Version: 8.0 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: 01 Nov 1996
Operational Range: 01 Jan 200 - 31 Dec 9999
Prerequisites: Office 97 Service Release 2 and Microsoft Jet 3.5 Update
Product Dependencies: Windows 95, Windows 98, or Windows NT 3.51 with SP 5 or greater, or Windows NT 4 (no specific SP is required, though SP 2 is recommended)
Clock Dependencies: System clock
Last Updated: 29 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 Office 97 Service Release 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:  

An acceptable deviation involving using Microsoft Access 97 to specify a two-digit date as a criteria in the QBE grid or in an object's property sheet has been discovered that may result in inconsistent dates depending on the system settings of the computer on which you run the query. For more information, and to download this update go to http://support.microsoft.com/support/kb/articles/Q172/7/33.asp

Download the Office 97 Service Release (SR) 2 Patch from http://officeupdate.microsoft.com/Articles/sr2fact.htm The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product. The issues addressed by this update exist in all Office 97 releases, including SR 1 and the base release.

How the product handles dates:

Storage. Microsoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time. See Knowledge Base article Q130514 for extended information.
Microsoft Access relies on the Jet database to store data. It uses shared VBA components to perform calculations on Date/Time data.

Formatting. Dates can be input in pre-defined and custom input formats, via an Input Mask. Input Masks enforce date entry in a particular format. Input Mask pre-defined formats include a Short Date format, which defaults to the Short Date format in the Regional Settings of the Control Panel when the mask is created. A custom Input Mask can be created to limit date entry to only 4-digit years. Microsoft Access does not require an Input Mask to enter dates. If an Input Mask is not used, the default behavior, dates can be entered in 2- or 4-digit year formats.
Dates can be displayed in pre-defined and custom formats, using the Format property and Format function. By default, dates are displayed in General Date format, which is a combination of Short Date and Short Time, as specified in the Regional Settings applet of the Control Panel. The General Date format will display dates inside of the 1930-2029 date window with two-digit years, dates outside this window will be displayed with four-digit years. Custom formats can be created to display years as 4-digits.

Parsing on date entry. Dates are parsed using OLE Automation. For more information, see the "OLE Automation Technology" Year 2000 compliance information document.

Two-digit shortcut handling:

Microsoft Access 97 interprets dates entered with a 2-digit shortcut to mean the 21st century in the following way.
1/1/00 through 12/31/29 are interpreted as 1/1/2000 through 12/31/2029
1/1/30 through 12/31/99 are interpreted as 1/1/1930 through 12/31/1999

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 the above section on 2-digit shortcuts).
Use Date/Time fields in tables to store date data. Avoid using Text fields to store date data.
Use a 4-digit year format to display dates. Avoid the use of the Short Date format (mm/dd/yy). Use the Long Date format (mm/dd/yyyy), the Short Date format in conjunction with the Regional Settings in the Control Panel, or a custom format to display all digits of the year (mm/dd/yyyy).
Text export, including the use of the VBA TransferText, method should always be set for export of four digit years.


Testing guidelines and recommendations:

In general, avoid testing in a production environment because one cannot predict side effects with other products.
The following areas should be looked at to verify dates are being properly used. The table below can be useful in testing Microsoft Access 97 within your organization.

TransferText, Import/Export

Tables, Queries, Forms, Reports, Macros, Modules

Import and Export of text files is available using the menus, the Transfer Text Macro Action, and in VBA code using the TransferText method.  Date data in 2-digit and 4-digit year format can be imported and exported using an Import/Export Specification. By default, dates are exported in a 2-digit year date format. The 4-digit year format can be selected when creating an Import/Export Specification.

Indexes

Tables

Date and time values can be indexed, and can require unique values.

Format

Tables, Queries, Forms, Reports, Modules

Provides formatting of Date/Time data in Tables, Queries, Form, Reports, and VBA Code. Exists as a property for Table, Query, Form and Report fields. Also implemented as an intrinsic function, Format(). Formats based on Regional Settings in Control Panel: Long Date, Short Date, Long Time Access Intrinsic Formats: General Date, Medium Date, Medium Time, Short Time Custom Formats: Any combination of month, day, year, and time

Input Mask

Tables, Queries, Forms, Reports, Modules

Limits user data entry to specific values. Values for Input Mask are derived from combinations of token characters such as (0, 9, and X), similar to custom Format properties. However, the validation and formatting of date data is done after the user has entered the data into the input masked field. Wizard defined input masks include: Short Date, Medium Date, Short Time, Medium Time, Long Time

Validation Rule

Tables, Queries, Forms

A Validation Rule is an expression that Access uses to verify data entered by the user. The Validation Rule expression can use Date/Time data from fields and perform comparisons on calculated date values.

Aggregate Queries

Queries

Users can group and sort queries on Date/Time fields. Aggregate queries also allow Date/Time fields to have totals calculated for the group date. The calculations allowed are: Sum, Avg, Min, Max, Count, StDev, Var, First, Last

Domain Functions

Queries, Forms, Reports, Modules

The Domain functions perform lookups and calculations on data and return the results. These functions are DAvg, DCount, DLookup, DFirst, DLast, DMin, DMax, DStDev, DStDevP, DSum, DVar, and DVarP.

Insert Date & Time

Forms, Reports

Inserts a calculated field that uses the Format function on the value of Date().

Charting

Forms, Reports

Forms and Reports can display charts that display Date/Time data based on a record source provided by Access.

Calendar Control

Forms, Reports, Modules

Value property allows user to get and set dates on calendar. Year is displayed as four digits.

Report Grouping

Reports

Reports can group and sort Date/Time data based on Each Value, Year, Qtr, Month, Week, Day, Hour, Minute.

Day(), Month(), Year(), WeekDay()

Queries, Forms, Reports, Modules

Parses Date/Time data.

Date(), Now()

Queries, Forms, Reports, Modules

Returns Date, and Date and Time

DateAdd(), DateDiff()

Queries, Forms, Reports, Modules

Performs calculations on Date/Time data.

LastUpdated, DateCreated properties

All database objects

Date/Time stamp of last update and object creation, provided by DAO.

CDate()

Queries, Forms, Reports, Modules

Valid ranges are -657434 (1/1/100) to 2958465 (12/31/9999). Time is stored in the decimal portion of the number.

     

   

To find more information on date related issues for this product:

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q162745

ACC: How to Convert Between Julian Days and Dates

Q109703

ACC: How to Find the Number of Days in a Month

Q168793

HOWTO: Change the Short Date Format from Visual Basic

Q149127

ACC: How to Determine If a Date Falls on a Weekend or Holiday

Q149095

ACC: How to Format Dates Regardless of Regional Settings

Q141536

ACC: How to Convert Short Time Format to Different Formats

Q132101

ACC: How to Get the Fiscal Year/Month of a Particular Date

Q95907

ACC: How to Display Only the Last Two Digits of Any Year

Q92816

ACC: Converting Julian Dates with Visual or Access Basic Code

Q88657

ACC: Functions for Calculating and Displaying Date/Time Values

Q103138

ACC: Function to Get Date of Monday Prior to Current Day

Q100136

ACC: Two Functions to Calculate Age in Months and Years

     

 

     

Informational Articles

Q130514

ACC: Storing, Calculating, and Comparing Date/Time Data

Q98802

ACC: Date/Time Data Type Provides Current Year Automatically

Q169599

ACC: Calendar Control Adds One Day When Time Is After 12:00 PM

Q155669

ACC: Years 00-29 Default to Year 2000 When Typed as M/D/YY

Q142009

ACC: How Windows Regional Settings Affect Microsoft Access

     

Other Date Issues

Q114832

ADT/ODE: Calendar Control Cannot Format Individual Dates

Q96897

ACC: Operation Stops When Editing Attached SQL Tables

Q160575

ACC: Can't Paste Append Using Input Mask Based on Short Date

Q159323

ACC: Importing Text File with Dates in DDMMMYY Format (95/97)

Q142184

ACC: Conversion Errors Importing Dates with Different Formats

Q130580

Incorrect Date Value Added to Properties Custom Tab

Q106290

ACC: Using Format() and Month() Returns Incorrect Month

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

ACC: Query w/Time Criteria Returns No Records from MS SQL Server

Access 97 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 97 please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 97 Microsoft Office document.


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


Microsoft Year 2000 Resource Center
Access Developers Toolkit  7.0   (Arabic)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Arabic OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details

How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data.

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (Dutch)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Dutch OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: None
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (English)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (French)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (German)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (Hebrew)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Hebrew OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (Japanese)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (Portuguese (Brazil))

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details

How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications. The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls. The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing. The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates. Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data. It uses shared VBA components to perform calculations on Date/Time data.

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95. See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95. Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
Access Developers Toolkit  7.0   (Spanish)

Product Summary
Product: Access Developers Toolkit Version: 7.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 01 Nov 1995
Operational Range: 01 Jan 100 - 31 Dec 9999
Prerequisites: none
Product Dependencies: Windows 95, or Windows NT 3.51 or greater; oleaut32.dll
Clock Dependencies: System Clock
Last Updated: 21 Jun 1999
Product Details


How the product handles dates:
Microsoft Access Developer's Toolkit for Windows 95 (ADT 95) contains several applications that aid in the development and distribution of Access 95 applications.  The applications included are the Help Workshop, Replication Manager and Transporter, Setup Wizard, Win32 API Viewer, Graph 5.0 run-time, and some OLE Custom Controls.  The OLE Custom Controls shipped with the ADT 95 are Comctl32.ocx, Comdlg32.ocx, Dblist32.ocx, Msdboutl.ocx, Richtx32.ocx, and Spin32.ocx.

The Help Workshop, Win32 API Viewer, and the OLE Custom Controls have no mechanisms for date parsing.  The Open and Save As common dialogs (in Comdlg32.ocx) are capable of displaying/sorting dates.  Display and sorting are determined by the Regional Settings applet in the Control Panel.

The Replication Manager and Transporter use Jet to store and manipulate data.  It uses shared VBA components to perform calculations on Date/Time data.  

The Setup Wizard uses Access 95 for date handling, since it is a wizard that is run under Access 95.  See the Microsoft Access 95 Year 2000 document for more information on how Access 95 handles dates.

The Graph 5.0 run-time displays date data on a graphical chart. Date data is either entered directly into the Graph 5.0 grid or imported from another application, such as Access 95.  Once the data is in Graph 5.0, dates are treated as serial dates and follow the same rules for date parsing as Access 95.

The OLE Custom Controls that ship with ADT 95 rely on date parsing from the hosting application.

Two-digit shortcut handling:
The ADT 95 components that are capable of displaying date data support 2-digit shortcuts for date display.
The ADT 95 components follow the same rules for converting 2-digit shortcuts as Access 95.

Common date usage errors:
See the common pitfalls and testing methods used in Access 95.

Testing guidelines and recommendations:

     

Known Issues

Q180081

ACC: Synchronization Fails When System Date Is Greater Than 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
ActiMates Arthur  1.0   (English)

Product Summary
Product: ActiMates Arthur Version: 1.0 Category:Compliant#
Language: English OS: Non-specific Release Date: 31 Aug 1998
Operational Range: 01 Jan 1998 - 31 Dec 2007
Prerequisites: NONE
Product Dependencies: Windows 95, Windows NT 4.0, all Oem Service Releases, all Service Packs, and greater
Clock Dependencies: Clock internal to the doll
Last Updated: 07 Jul 1999
Product Details



Description of how the product handles dates:
The ActiMates dolls contain an internal clock. This clock references an internal hard-coded look-up table of major holidays with varied calendar days (i.e. Easter, Thanksgiving) through 12/31/2007.

What are the issues?:
After 12/31/2007, lose some minor functionality. First, only fixed holidays (i.e. Independence Day) will be recognized and announced by the character after this date. In addition, the character will not recite the year when announcing the date and time. No immediate action is required to have the doll maintain functionality through the change in the millennium.


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
ActiMates Barney  1.0   (English)

Product Summary
Product: ActiMates Barney Version: 1.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites:
Product Dependencies:
Clock Dependencies:
Last Updated: 07 Jul 1999
Product Details

Description of how the product handles dates:

ActiMates Barney does not maintain an internal clock. There are no date issues with this product.


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
ActiMates DW  1.0   (English)

Product Summary
Product: ActiMates DW Version: 1.0 Category:Compliant#
Language: English OS: Non-specific Release Date: 31 Aug 1998
Operational Range: 01 Jan 1998 - 31 Dec 2007
Prerequisites: NONE
Product Dependencies: Windows 95, Windows NT 4.0, all Oem Service Releases, all Service Packs, and greater
Clock Dependencies: Clock internal to the doll
Last Updated: 07 Jul 1999
Product Details



Description of how the product handles dates:
The ActiMates dolls contain an internal clock. This clock references an internal hard-coded look-up table of major holidays with varied calendar days (i.e. Easter, Thanksgiving) through 12/31/2007.

What are the issues?:
After 12/31/2007, lose some minor functionality. First, only fixed holidays (i.e. Independence Day) will be recognized and announced by the character after this date. In addition, the character will not recite the year when announcing the date and time. No immediate action is required to have the doll maintain functionality through the change in the millennium.


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
ActiveMovie  1.0   (Basque)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Basque OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Catalan)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Catalan OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Chinese - Simplified)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Chinese - Traditional)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Chinese - Traditional OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Czech)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Czech OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Danish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Danish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Dutch)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Dutch OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (English)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Finnish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Finnish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (French)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (German)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Greek)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Greek OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Hungarian)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Hungarian OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Italian)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Japanese)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Korean)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Korean OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Norwegian)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Norwegian OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Polish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Polish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Portuguese (Brazil))

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Portuguese)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Portuguese OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Russian)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Russian OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Slovak)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Slovak OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Slovenian)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Slovenian OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Spanish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Swedish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Swedish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveMovie  1.0   (Turkish)

Product Summary
Product: ActiveMovie Version: 1.0 Category:Compliant
Language: Turkish OS: 32-Bit Win Release Date: 01 Oct 1996
Operational Range: 01 Jan 1900 - 31 Dec 2099
Prerequisites: None
Product Dependencies: Windows 9x, Windows NT4 Service Pack 3, Windows 2000, Internet Explorer 3, Internet Explorer 4.x, Internet Explorer 5.x, DirectX.
Clock Dependencies: System Clock, DCOM, COMCTL, OLEAUT32
Last Updated: 14 Jul 1999
Product Details

Note: There have been no internationalization concerns identified. Thus this product is not dependent on an English language platform for compliance.

See DirectX Media for information about newer versions of this product.

How the product handles dates:

ActiveMovie internals do not manipulate dates.

A copyright can be stored in the RIFF headers of some media files (e.g. AVI), but this is stored as a text string. The authoring date is entered into the file by the authoring tools and not manipulated by ActiveMovie. In addition there are the system attributes for file creation, access, and modification dates, but these are not accessed or used by ActiveMovie.

Two-digit shortcut handling:

Not applicable.

Testing guidelines and recommendations:

Begin playback of a media file and change the system date to a post-year 2000 date. Perform playback of media files authored with both pre-year 2000 dates as well as post-year 2000 dates. If users are streaming playback from a server, the server system date would need to be changed to post-year 2000. Fully evaluate the potential effects before implementing. It is recommended this testing be done on non-productions systems.


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
ActiveStore Sys. Framework Svcs.  1.0   (English)

Product Summary
Product: ActiveStore Sys. Framework Svcs. Version: 1.0 Category:Compliant
Language: English OS: Win NT Release Date: 07 Jun 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Windows NT 4.0 Service Pack 3 or higher, Internet Explorer 4.X or higher, SQL Server 6.5 Service Pack 3 or higher, ADO 2.1, MSMQ 1.0 or higher.
Clock Dependencies: None
Last Updated: 22 Jun 1999
Product Details

How the product handles dates:

This product does not perform date calculations. There are no interfaces (user interface or programmatic) to provide dates to System Framework Services. This product does not deal with dates directly. There is no ActiveStore System Framework Services source code that uses dates, but it uses SQL Server, ADO, Visual C 6.0, and Visual Basic 6.0 that might use dates.

Two-digit shortcut handling:

Not Applicable.

 

 

 


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


Microsoft Year 2000 Resource Center
ActiveSync  3.0   (English)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (French)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (German)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (Italian)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (Japanese)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 22 Oct 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 09 Nov 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (Portuguese (Brazil))

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ActiveSync  3.0   (Spanish)

Product Summary
Product: ActiveSync Version: 3.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 30 Jul 1999
Operational Range: -
Prerequisites: None
Product Dependencies: Schedule+ 7.0a, Schedule+ 7.5, Outlook 97, Outlook 98, or Outlook 2000; Windows 95, Windows 98, or Windows NT 4.0; and Windows CE Handheld PC or Palm-sized PC
Clock Dependencies: Windows CE OEM, Windows CE Operating System
Last Updated: 21 Sep 1999
Product Details

Operational Range for Data: Depends on Windows CE operating system, OEM device, desktop PIM software used, and Windows CE-based device PIM software.

How the product handles dates:

ActiveSync synchronizes data between the desktop machine and Windows CE devices. Dates are stored and manipulated as 4-digit dates.

ActiveSync does not accommodate direct manipulation or methods for entering date information. The user enters data using the PC’s or device’s PIM software.

On the device, Calendar and Task programs support date ranges from 1/1/1900 to 12/31/2999. For Contacts (birthday and anniversary) there is no restriction on the date range – it just has to be above 1/1/1601 and translate into a FILETIME structure with the special case that 1/1/4501 is the special date "None" (where the contact does not contain a birth date or anniversary date).

OEM hardware typically only supports a 100-year range – primarily between 1970 and 2069.

For more information see the year 2000 compliance documentation for Outlook, Schedule+, and the Windows CE operating system.

 

Two-digit shortcut handling:

Not Applicable.

 

Testing guidelines and recommendations:

In general, avoid testing in a production environment because side effects with other non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products and with Exchange Server can be conducted safely. Note that reminders for future appointments or tasks may fire during this testing and will not re-notify when date is set back.


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
ADO  1.0   (English)

Product Summary
Product: ADO Version: 1.0 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1996

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Chinese - Simplified)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Chinese - Traditional)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Czech)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Czech OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Danish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Danish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Dutch)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Dutch OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (English)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Finnish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Finnish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (French)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (German)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Greek)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Greek OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Hungarian)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Hungarian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Italian)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Japanese)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Korean)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Norwegian)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Norwegian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Polish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Polish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Portuguese (Brazil))

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Portuguese)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Portuguese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Russian)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Slovak)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Slovak OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Slovenian)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Slovenian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Spanish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Spanish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Swedish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Swedish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  1.5   (Turkish)

Product Summary
Product: ADO Version: 1.5 Category:Compliant*
Language: Turkish OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1997

Version 1.5 shipped in the Window NT Server Option Pack, Windows NT Workstation, Windows 95.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Chinese - Simplified)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Chinese - Simplified OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Chinese - Traditional)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Chinese - Traditional OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (English)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: English OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (French)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: French OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (German)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: German OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Italian)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Italian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Japanese)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Japanese OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Korean)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Korean OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
ADO  2.0   (Russian)

Product Summary
Product: ADO Version: 2.0 Category:Compliant*
Language: Russian OS: 32-Bit Win Release Date: N/A
Operational Range: -
Prerequisites: Windows NT 4 Service Pack 3 or higher, or Windows 9x operating systems
Product Dependencies: OLE32, OLEAUT32, OLEDB (msdadc.dll, the Data Coercion Library), Data Sources (Servers), Visual Basic for Applications, expsrv.dll, msvcrt.dll, msvbrtm.dll
Clock Dependencies: NONE
Last Updated: 11 Nov 1998
Product Details

Operational Range for Data: Data Source Dependent

Release Date: 1998

Version 2.0 shipped in Visual Studio.

How the product handles dates:

ADO is not a storage component and only deals with date conversion when handling variants (usually string-to-date conversions). Date conversions are performed through OLE’s VariantChangeType() and the OLEDB Data Coercion service.

Two-digit shortcut handling:

OLE Automation (OLEAUT32.DLL) and OLE DB’s Data-Coercion library (which also relies on OLE for this conversion) are used to convert strings to date format. See the OLE DB Year 2000 statement for possible issues with OLE DB data conversion.

Common date usage errors:

Users should use 4-digit years when storing data or calling methods/properties of the MDAC object models. Using 2-digit years may reveal year-windowing in your backend or provider, where the boundary cases may not be well known (given an arbitrary backend data store).

Testing guidelines and recommendations:

Since there is some "windowing" inherent in the date features of OLE and most backend data stores, users should use 4-digit year formats in dates, particularly when placing data into a store and querying that store.


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


Microsoft Year 2000 Resource Center
Age of Empires  1.0   (English)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: English OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (French)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: French OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (German)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: German OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (Italian)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: Italian OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (Japanese)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: Japanese OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (Portuguese (Brazil))

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: Portuguese (Brazil) OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  1.0   (Spanish)

Product Summary
Product: Age of Empires Version: 1.0 Category:Compliant
Language: Spanish OS: 32-Bit Win Release Date: 14 Sep 1997
Operational Range: -
Prerequisites: None
Product Dependencies: DirectX 5.0, DirectPlay 5.0a, Indeo 4.1, Windows NT
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

This document applies to:

Age of Empires v.1 (released September 14, 1997)

Age of Empires: Rise of Rome v.1 (released September 17, 1998)

Age of Empires Gold Edition v.1 (released January 10, 1999)

How the product handles dates:

Age of Empires does not accept user entered dates.

Two-digit shortcut handling:

Not Applicable.

Note that the following applications exist on the CD. They are not required for playing the game. Their Year 2000 compliance is not included.

Age of Empires v.1

MSInfo versions 2.51.0.0808

Internet Explorer version 3.02

Age of Empires: Rise of Rome v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Urban Assault

Close Combat 2

Gaming Zone A501

Age of Empires Gold Edition v.1

MSInfo versions 2.51.0.0808

Adobe Acrobat Reader version 3.01

DX5Test version 1.0

DX Diag version 4.06.00.0318

DX Info version 4.05.00.0155

DX Tool version 4.05.00.0155

DirectPlay 6.0a

MS Sampler version 1.00.0005, which is a shell that launches the following applications:

Gaming Zone A501

 

 


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
Age of Empires  2.0   (Chinese - Simplified)

Product Summary
Product: Age of Empires Version: 2.0 Category:Compliant
Language: Chinese - Simplified OS: 16-Bit Win Release Date: 15 Sep 1999
Operational Range: 15 Sep 1999 - 31 Dec 2035
Prerequisites: None
Product Dependencies: DirectX 6.1, DirectPlay 6.1a
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

How the product handles dates:

Microsoft Age of Empires II: The Age of Kings stores dates for recorded games in the following format:

recorded game – DD-month-YYYY time(hh`mm`ss)

Example: recorded game – 31-Dec-2000 00`36`32

Two-digit shortcut handling:

The product does not use 2-digit-year shortcuts.


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
Age of Empires  2.0   (Chinese - Simplified)

Product Summary
Product: Age of Empires Version: 2.0 Category:Compliant
Language: Chinese - Simplified OS: 32-Bit Win Release Date: 15 Sep 1999
Operational Range: 15 Sep 1999 - 31 Dec 2035
Prerequisites: None
Product Dependencies: DirectX 6.1, DirectPlay 6.1a
Clock Dependencies: System clock
Last Updated: 14 Oct 1999
Product Details

How the product handles dates:

Microsoft Age of Empires II: The Age of Kings stores dates for recorded games in the following format:

recorded game – DD-month-YYYY time(hh`mm`ss)

Example: recorded game – 31-Dec-2000 00`36`32

Two-digit shortcut handling:

The product does not use 2-digit-year shortcuts.


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.