This article was previously published under Q183125
This article has been archived. It is offered "as is" and will no longer be updated.
When you use the document Properties viewer to define a custom propertyto include a date type in a file, the year may not be saved correctly.For example, if you select a Microsoft Project data file (*.mpp) in afolder window, chose Properties on the Explorer window File menu, clickthe Custom tab click Date in the Type field, enter a value of 01/01/01,and then click Add, the date appears as 01/01/1901 rather than 01/01/2001.
Windows NT 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
The English version of this post-SP3 hotfix has been posted to the following Internet locations.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
For more information on what is fixed in Y2K2-fix, please see the followingarticles in the Microsoft Knowledge Base:
175093 User Manager Does Not Recognize February 2000 As a Leap Year
183123 Find Files Displays Garbled Date if Year is 2000 or Greater
184132 Err Msg: Value Entered Does Not Match with the Specified Type
186669 FPNW Logout.exe Incorrectly Reports Year After Jan. 1, 2000
191768 Date of Print Job May Be Displayed Incorrectly in Print Queue
193056 Problems in Date/Time after Choosing February 29 in a Leap Year
193434 Migration Changes NetWare Accounts Expiration Date
194726 FPNW Client Does Not Get Correct Time or Date After Y2K
207799 IBM PS/1 will not Boot on or After January 1, 2000