![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif)
Microsoft Year 2000 Readiness Disclosure & Resource Center |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) |
![](/file/18315/Y2K_Resource_Nov99.iso/webcon~1/usa/year2k/images/spacer.gif) | Access 95 7.0 (Russian) - 32-Bit Win
Product Summary |
Product: Access 95 Version: 7.0 |
Category: Compliant* Operating System: 32-Bit Win |
Language: Russian |
Release Date: 01 Sep 1995 |
Operational Range: |
01 Jan 200 - 31 Dec 9999 |
Prerequisites: |
OLEAUT32.DLL ver. 2.20.4054 or later and Office 95 Year 2000 Software Update |
Product Dependencies: |
Windows 95 or Windows NT 3.51 or greater |
Clock Dependencies: |
System clock, OLEAUT32.DLL |
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 95 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.
Prerequisite
An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/rus/downloadDetails/O95y2k.htm.
Description of 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 forces users to enter dates in a 2-digit format. 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. 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. Parsing on date entry. OLEAUT32. 2.20.4054 or higher is required in order for Access 95 to correctly recognize 2-digit date shortcuts as falling within a window between 1930 and 2029. Without that file update, Access assumes that all shortcut dates fall in the current century. |
Two-digit shortcut handling:
Microsoft Access 95's interpretation of dates depends on the version OLEAUT32.DLL in the system folder.
If your OLEAUT32.DLL has a version of 2.20.4054 or greater, Access 95 interprets dates entered with an abbreviated year format, to mean the 21st century. Office97 and Windows NT 4.0 install a version of OLEAUT32.DLL that follows these rules.
For more information, see The Automation Libraries and the Year 2000 whitepaper"
|
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 |
If your version of OLEAUT32.DLL is less than 2.20.4054, Access 95 interprets dates entered with an abbreviated year format to mean the current century in the following way. Windows 95 installs a version of OLEAUT32.DLL that follows these rules.
If the current century is the 20th: 1/1/00 through 12/31/99 are interpreted as 1/1/1900 through 12/31/1999 If the current century is the 21st: 1/1/00 through 12/31/99 are interpreted as 1/1/2000 through 12/31/2099
What are the acceptable deviations?
Dates with two digit years in imported text files are interpreted as falling in the twentieth century. Users can avoid this behavior by importing the files as text rather than as date type, then setting the field type to date. Dates at that point will be interpreted using Access's own date window of 1930-2029. Additionally, database synchronization may fail when spanning the century boundary. This behavior is correction in the Office 95 Year 2000 Software Update. This behavior is correction in the Office 95 Year 2000 Software Update.
To determine the version of OLEAUT32.DLL you have:
a) Click on the Start button. Go to Find > Files or Folders b) Enter Oleaut in Named Section; Choose [C:] to look in c) Highlight Oleaut 32.dll d) Click on File > Properties e) Select the Version tab: |
|
If File version is 2.20.4054 or higher the below download is not required.
If File version is less than 2.20.4054, the below download is necessary for Access to follow the 2-digit date window of 1930-2029.
|
Download OLEAUT32.DLL version 2.20.4118
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, 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 Microsoft 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 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 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. |
|
|
Is there any place 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 |
|
|
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 |
|
|
Q169156 |
|
ACC95: DateDiff, DateAdd, or DatePart Causes IPF in VBA232.DLL |
|
|
Q149945 |
|
ACC95: Parameter Query Excludes Ending Date |
|
|
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 |
|
|
Q104973 |
|
ACC: DateDiff() Function Returns Incorrect Value |
|
|
Access 95 uses a number of Microsoft Office 95 shared files for the implementation of dialogs and toolbars, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Access 95, 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 95 Microsoft Office document. | |
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.
|