Microsoft Year 2000 Readiness Disclosure & Resource Center

Product Summary

Product: Project Version: 4.0 Category: Compliant* Operating System: 16-Bit Win Language: Swedish Release Date: 01 Apr 1994 Operational Range: 01 Jan 1984 - 31 Dec 2049 Prerequisites: For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) Product Dependencies: Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. Clock Dependencies: System Clock Last Updated: 06 Nov 1998

Product Details

Description of how the product handles dates: Storage. Microsoft Project stores all dates in a 32-bit data structure in the form of minutes from January 1, 1984. This circumvents the possibility that a date may be stored with a 2-digit year because the date and year are not stored, only the duration since January 1, 1984. Microsoft Project schedules projects within a finite time period extending from January 1, 1984, to December 31, 2049. Project does not allow any tasks outside these bounds. Parsing on date entry. Microsoft Project includes date entry points in which users may enter a date. Project allows and processes entries with 2-digit years. However, since ProjectÆs calendar doesnÆt span an entire century, the product always interprets 2-digit year entries in the correct century.   2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors: The core application of MS Project recognizes only dates within the 1984-2049 timeframe. Accordingly, any given date must either be in the 20th or 21st century resulting in unambiguous resolution of dates based on the 1984-2049 date window. For example, if you enter the date 1/1/01, Microsoft Project correctly recognizes this as 1/1/2001. Under some circumstances described in the Product Guide for the Visual Basic Development Environment, custom programming features of Visual Basic may improperly recognize a 2-digit year as being in the 21st century instead of the 20th century. If applied against project data, the internal year boundaries in Microsoft Project (1984û2049) will prevail and the entry will be rejected. Leveling operations that attempt to schedule work past the end of 2049 cause the duration to be zeroed. When using the Save to Database functionality in Microsoft Project 4.0 any dates in the year 2000 are incorrect. For example, "4/15/2000" is changed to "4/15/100" instead of "4/15/00". When opening from the database, an error is generated stating that the date is invalid; the date is ignored. Download the updated version of PROJ2ACC.DLL below to resolve this date usage issue. Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following: Copy the file to your Windows System directory or folder. For example, if you have the English version of Microsoft Project, copy the file Engprj2a.exe to your Windows System directory. NOTE: You cannot mix languages. For example, if you have the English version of Microsoft Project, you cannot use the Spanish version of the Save to Database file contained in Spnprj2a.exe. Run the file you copied in step number 1. For example, in the Windows File manager, change to your Windows System directory, click the file name and, on the File menu, click run. Click OK. You may get the message, Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. If you wish, you can delete the file copied in Step 1. 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 examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0 Sub-system Component File File Native File Types MPX Mail Mail-Set Rem Mail-Workgroup Posting Misc. Boot / Exit Calendar Costing Custom Field DDE / OLE Sheet Links Environment Filters Import / Export Macros Options Sort Subproject Summary Tasks Timescale Tracking VBA Language   Scheduling Engine Calculation Date Entry Leveling Proj Info Res Assign Resource Res Sharing Schedule-Autolink Schedule-links Schedule- Pred / Succ Schedule- Recurring Task Schedule- Res Schedule- Task Schedule- Task Constraint Work View View Res Usage View- Calendar View- Gantt View- Graph View- Pert View- Sheets View- Task PERT

Return to Search Screen

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

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.

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.