Microsoft Y2K  
Microsoft
 This static CD-based web site is representative of the www.microsoft.com/y2k site as of October 15, 1999.

Microsoft Year 2000 Readiness Disclosure & Resource Center
Access 2.0   (Portuguese (Brazil)) - 16-Bit Win

Product Summary
Product: Access 2.0
Version:
Category: Compliant*
Operating System: 16-Bit Win
Language: Portuguese (Brazil) Release Date: 01 Apr 1994
Operational Range: 01 Jan 0100 - 31 Dec 9999
Prerequisites: Access 2.0 software update: Two-Digit Date Patch (see below)
Product Dependencies: Windows 3.1, or Windows NT 3.0 or greater
Clock Dependencies: System Clock
Last Updated: 01 Oct 1999
Product Details

The compliance of Access 2.0 has changed from Not Compliant to Compliant* with the release of the Access 2.0 software update. See below for details.

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

Recommendations to meet compliance:

Obtain a software update from the following article in the Microsoft Knowledge Base:

Q231408 ACC2: Access 2.0 Two-Digit Date Patch Available on MSL

The Microsoft Access 2.0 Two-Digit Date Patch enhances the following functionality:

1. Access 2.0 will interpret 2-digit year dates based on a setting in the WIN.INI file. By default, Access 2.0 will interpret 2-digit year dates in the 1900-1999 range, which is the productÆs behavior before the Two-Digit Date Patch is installed. If a user has the following section and settings in their WIN.INI file, Access 2.0 will use a date window based on a 100-year range, with the ending year being the value specified by the TwoDigitYearMax value.

[Microsoft Access 2.0] TwoDigitYearMax=2029

The above settings in the WIN.INI file will change the date window for users on that machine to interpret two-digit year dates in the range 1930-2029.

Two-digit years from 00 to 29 are interpreted as 2000 to 2029.

Two-digit years from 30 to 99 are interpreted as 1930 to 1999.

 

2. Access 2.0 will store literal dates entered in property sheet values and in the query designer with 4-digit years.

3. Access 2.0 will interpret a date without a year as being in the current year of the system clock in years 2000 and later.

4. Access 2.0 will now display literal dates in modules with 4-digit years.

5. Access 2.0 will import text files using the 1930-2029 date window.

 

See Microsoft Knowledge Base Article Q75455 for more information on the Microsoft Access 2.0 Two-Digit Date Patch.

Common date usage errors:

  • Using the Short Date Input Mask will limit users' ability to enter dates outside of the 2-digit year short cut 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, 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 we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify dates are being properly used. The table below can be used to guide testing of Access within your organization.

Functionality

Areas Affected

Testing Notes

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 look-ups 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 always 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.

 

Are there other known issues in the product that are date related?

     

How To Articles

Q162718

HOWTO: Prepare Visual Basic Applications for the Year 2000

Q109703

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

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

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

Q125003

ACC: DateDiff() Ignores Start Date, Not End Date, with "ww"

Q106290

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

Q103996

ACC: Imported Microsoft Excel Date Fields Are Off by 4 Years

Q103174

ACC: Exporting Date Fields to Text Includes Time Format

Q173097

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

Q104973

ACC: DateDiff() Function Returns Incorrect Value

Return to Search Screen

Legend of Symbols:
* The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
# The product is compliant with acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product.
+ The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

If after reviewing this information you have additional questions related to this product, click here.

 

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://www.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.


 

Monday, October 4, 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.