Microsoft TechNet - Year 2000



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

Year 2000

	Compliance Statement
	FAQs
	Product Guide
	Services
	Tools
	White Papers

The Automation Libraries and the Year 2000

In efforts to improve code efficiency and lower the total cost of ownership for our products, Microsoft has recommended to internal developers to use a common Automation Library for handling dates. Over the years, the library has been updated to reflect changing customer needs and add additional functionality. Updated versions of the library are installed with major product releases such as Microsoft Office, Microsoft Visual Studio and Microsoft Internet Explorer.

How do I know if I have the automation library?

If you're running Windows 95 or Windows NT 3.51 or later, then you use the automation library.

What makes up the automation library?

Four files make up the automation library. These files are:

oleaut32.dll
olepro32.dll
asycfilt.dll
stdole2.tlb

These files are installed either by the operating system or an application.

How does the automation library affect year 2000 issues?

The automation library contains routines for interpreting two digit years and provides a convenient way for applications to create unambiguous (serial) dates. So, many of your applications probably use the automation libraries for date handling.

Over the years the automation libraries have been revised three times with regards to their date formatting behavior:

Library (OLEAUT32.DLL) Version Two Digit Year Cutoff

Before 2.20.00.4054 1999

Versions 2.20.00.4054 to 2.29.xx.xxxx inclusive 2029

Versions 2.30.00.xxxx and forward User determined

How do I know what version of the automation libraries my computer has?

Click the Start button, select the Find menu item, and click on "Files or Folders..." In the "Name & Location" tab, type (without quotes) "oleaut32.dll" in the field titled "Named." Select the drive in the "Look in" field that your operating system lives on (usually (C:) ). Click "Find Now." When the file shows up in the box below, right click on the file and select "Properties." Click the right hand tab that says "Version."

Name some applications that use automation libraries

Microsoft Office 95 and later
Microsoft Visual Studio (including Visual C++, Visual Basic, Visual Interdev and custom applications)
Microsoft Windows 95, Windows 98, Windows NT Workstation, Windows NT Server
Microsoft Internet Explorer

What are the implications for the organization with multiple versions of the automation libraries?

There are a few year 2000 issues that could result from different users having different versions of the automation libraries. These all involve the interpretation of years entered with only two digits. If your software applications and users enter four digit years, there are no problems. If your users or software are entering two digit years, then a scenario where different machines are entering years in different centuries is possible. For example, a data entry department could be running a custom application on both Windows NT 3.51 (without service packs) and on Windows NT 4.0 Workstation. If the users are entering dates like 1/1/10, the NT 3.51 machines could record the date as January 1, 1910 while the NT 4.0 machines may record January 1, 2010. By installing the latest service packs or newer applications (like Microsoft Office 97 or Internet Explorer 4.0), you can assure that your systems have more consistent date handling.

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