| Microsoft Year 2000 White
Papers |
|
|
|
C
Runtime Libraries and the Year 2038 Issue
After January 18,
2038, applications that rely on the 32-bit ANSI C time_t data type
may not function as expected. Read this whitepaper to find out more
about C Runtime and the year 2038 issue. 
The
Four-Digit Year-a Good Practice for Office
Documents
There are several simple
steps you can take to avoid confusing date formats as the year 2000
approaches. Read this whitepaper to find out more.
Using Systems Management Server 2.0 for Year 2000
Analysis
Microsoft« Systems
Management Server version 2.0 contains tools that centrally audit
hardware and software for year 2000 compliance. Read more on the use
of these tools for querying and reporting.
Meeting the Year 2000 Challenge
Microsoft Office
2000 applications are ready for the year 2000, but there are
additional steps you can take to prepare for the transition to the
next millennium.
ANSI
Time and Visual C++ Libraries
An application can appear to
have a year 2000 issue because of how ANSI functions are permitted
to behave. You can create year 2000 compliant applications and avoid
confusing output from your programs if you follow some simple
guidelines when using ANSI functions. Read this whitepaper to learn
the guidelines to follow.
Visual SourceSafe 5.0 Year 2000
Update
This whitepaper is designed
exculsively for machines with Visual SourceSafe 5.0 installed. The
issues described in this paper are cosmetic display issues. There
are no known issues that impact the storage of files or project data
across to the year 2000. Read this whitepaper to find out what the
issues are.
Year
2000 Date Support in FoxPro
For FoxPro and Visual FoxPro
developers, the transition to the year 2000 presents a number of
issues to be aware of so that the applications you build will be
fully year 2000 compliant and function with the behavior you desire
after the turn of the century. This paper is meant to help you
identify year 2000 issues that may be present in your applications
and to suggest solutions that you can provide.
Developing Year 2000 Compliant Applications in Microsoft
Visual Basic
Microsoft believes that the
following material, excerpted from the book entitled Advanced Visual
Basic 6.0 by The Mandelbrot Set International (ISBN: 1572318973),
provides developers on year 2000 issues.
Date Migration Tools for Excel 97
Three date
migration add-in tools for Microsoft Excel 97 can help you to
prepare dates in Excel workbooks for transitioning from earlier
versions of Excel or for auditing workbooks for the year 2000. Read
this article to learn about the Date Fix Wizard, Date Migration
Wizard, and Date Watch Wizard.
Updating Your Date Settings for the Year
2000
You can change settings in
your operating system to display dates with 4-digit years in both
Microsoft Office 97 and Office 2000, as well as change the way
Office 2000 interprets 2-digit years. Find out how in this
whitepaper.
Visual C++ and the Year 2000
This whitepaper
details information on Visual C++ and explores the technical issues
involved with Visual C++ and date handling issues. Find out how to
verify and fix date issues in a software system, suggested
practices, and additional y2k resources.
Preparing Office Solutions for the Year
2000
This paper is designed to
explain Year 2000 issues related to custom solutions built using
Microsoft Office and Visual Basic for Applications. If you develop
custom solutions using Microsoft Office, you should read this paper
to assess any potential problems that might arise from operating
those solutions past December 31, 1999. The material presented
illustrates potential areas for concern and the steps required to
address any issues.
Microsoft Operating System Interactions with BIOS and
Real Time Clock
This paper addresses the
interaction of the computerÆs Real Time Clock (RTC) and basic
input/output system (BIOS) with the following Microsoft« operating
systems: Windows NT« version 3.51, Windows NT« version 4.0, Windows«
98, Windows« 95, Windows« 3.x, and MS-DOS« version 5.x or later.
Windows« operating systems insulate applications from most, although
not all, Year 2000 rollover issues.
Year 2000 Test Considerations
The information
in this paper should be viewed as high-level testing recommendations
which organizations can use to scope and implement their year 2000
efforts.
Ctime
The information in this
paper pertains to Ctime and the impact that it has on productsÆ
ability to work into the 21st century. Ctime is a function of the C
programming language that is used to calculate time.
The
Automation Libraries and the Year 2000
The information
in this whitepaper has been revised and can now be found in the OLE
Automation Product Guide document. Please update your bookmarks.
Building Year-2000 Compliant Applications with Visual
Studio and Windows DNA
The Microsoft« Windows DNA
architecture represents a comprehensive new framework for
integrating client/server and internet software solutions on the
Windows platform. Windows DNA is based on the premise of software
component integration and interoperability. DNA combines "component
based" software development with a "service based" operating system.
However, integrated software components and modularity do not
protect the developer from introducing Year 2000 compliance problems
in their applications. Regardless of the tools used to develop
software today, a clear Year 2000 philosophy is needed to avoid
spending time reworking an application in future years.
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.
|
