| Microsoft Year 2000 Readiness Disclosure & Resource Center |
|
|
| Project 98 (Italian) - 32-Bit Win
| Product Summary |
Product: Project
Version: 98 |
Category: Compliant
Operating System: 32-Bit Win |
| Language: Italian |
Release Date: 01 Sep 1997 |
| Operational Range: |
01 Jan 1984 - 31 Dec 2049 |
| Prerequisites: |
none |
| Product Dependencies: |
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater |
| Clock Dependencies: |
System Clock |
| Last Updated: |
13 Oct 1999 | |
| Product Details |
|
The findings covered in this document apply to the base version of Project 98 and to Service Release 1.
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 does not span an entire century, the product always interprets 2-digit year entries in the correct century.
Two-digit shortcut handling:
Conversion of 2-digit shortcut assumes a date window of 1984 through 2049.
Common date usage errors:
The core application of Microsoft 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 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 2000s instead of the 1900s. 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.
The VBA Timescaled data method returns an incorrect value when used on dates in 2049.
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 Project within your organization.
Microsoft Project 98
|
Sub-system |
Component |
|
Database |
DB Integrity |
|
File |
File Native File Types MPX |
|
Mail |
Mail-Set Rem Mail-Workgroup Outlook Journal 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 Resource Contouring Res Assign Res Avail Resource Res Sharing Schedule-Autolink Schedule-links Schedule- Pred / Succ Schedule- Recurring Task Schedule- Res Schedule- Task Schedule- Task Constraint Schedule- Tsk Split Work |
|
View |
View Res Usage / Graph View- Calendar View- Gantt View- Graph View- Pert View- Sheets View- Task PERT View- Usage |
Project 98 uses a number of Microsoft Office 97 shared files for the implementation of dialogs and toolbars, task automation, online help, installation, graphics, file find and file I/O. For additional information that is appropriate for Project 98, please refer to any version 97 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.
|
