Product Summary
Product: Project	Version: 98	Category:Compliant#
Language: Hebrew	OS: 32-Bit Win	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:	14 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: For all Hebrew Office 97 applications and with the exception of Outlook 97, if the user enters a date that uses a two-digit year in the Custom tab of the Properties dialog box, the date will be formatted with a value between 1900 - 1999. As an example the user does the following: Selects Properties or Database Properties from the File menu. Clicks the Custom tab. Enters a field name in the Name edit box. Selects date from the Type list. Enters the value 7/5/00 in the value field. Clicks Add. The date will appear in the properties list box as 7/5/1900, not 7/5/2000. For information check the Knowledge Base Article Q186261. Storage.  Microsoft Project stores all dates in a 32-bit data structure (years are stored with all 4-digits) 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 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 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.    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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Italian	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Japanese	OS: 32-Bit Win	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 3 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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Korean	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Norwegian	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Portuguese (Brazil)	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Portuguese	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Spanish	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Project	Version: 98	Category:Compliant
Language: Swedish	OS: 32-Bit Win	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.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 1.0	Category:Compliant
Language: English	OS: Win NT	Release Date: 01 Oct 1996
Operational Range:	01 Jan 1950 - 31 Dec 2049
Prerequisites:	None
Product Dependencies:	Windows NT4 Service Pack 4 (Internet Information Server 3)
Clock Dependencies:	Operating System clock
Last Updated:	21 Sep 1999
Product Details
How the product handles dates: Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Windows NT file system. Service Uses dates? Compliance Issues Date Algorithm HTTP Proxy Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. WinSock Proxy No None N/A SOCKS Proxy No None N/A Cache Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Logging Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.   Two-digit shortcut handling: Interpretation of 2-digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate proxy and firewall operation with Proxy Server, web server and browser by setting system clocks to years before equal to and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 1.0	Category:Compliant
Language: French	OS: Win NT	Release Date: 01 Oct 1996
Operational Range:	01 Jan 1950 - 31 Dec 2049
Prerequisites:	None
Product Dependencies:	Windows NT4 Service Pack 4 (Internet Information Server 3)
Clock Dependencies:	Operating System clock
Last Updated:	21 Sep 1999
Product Details
How the product handles dates: Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Windows NT file system. Service Uses dates? Compliance Issues Date Algorithm HTTP Proxy Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. WinSock Proxy No None N/A SOCKS Proxy No None N/A Cache Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Logging Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.   Two-digit shortcut handling: Interpretation of 2-digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate proxy and firewall operation with Proxy Server, web server and browser by setting system clocks to years before equal to and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 1.0	Category:Compliant
Language: German	OS: Win NT	Release Date: 01 Oct 1996
Operational Range:	01 Jan 1950 - 31 Dec 2049
Prerequisites:	None
Product Dependencies:	Windows NT4 Service Pack 4 (Internet Information Server 3)
Clock Dependencies:	Operating System clock
Last Updated:	21 Sep 1999
Product Details
How the product handles dates: Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Windows NT file system. Service Uses dates? Compliance Issues Date Algorithm HTTP Proxy Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. WinSock Proxy No None N/A SOCKS Proxy No None N/A Cache Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Logging Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.   Two-digit shortcut handling: Interpretation of 2-digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate proxy and firewall operation with Proxy Server, web server and browser by setting system clocks to years before equal to and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 1.0	Category:Compliant
Language: Japanese	OS: Win NT	Release Date: 01 Oct 1996
Operational Range:	01 Jan 1950 - 31 Dec 2049
Prerequisites:	None
Product Dependencies:	Windows NT4 Service Pack 4 (Internet Information Server 3)
Clock Dependencies:	Operating System clock
Last Updated:	21 Sep 1999
Product Details
How the product handles dates: Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Windows NT file system. Service Uses dates? Compliance Issues Date Algorithm HTTP Proxy Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. WinSock Proxy No None N/A SOCKS Proxy No None N/A Cache Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Logging Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.   Two-digit shortcut handling: Interpretation of 2-digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate proxy and firewall operation with Proxy Server, web server and browser by setting system clocks to years before equal to and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 1.0	Category:Compliant
Language: Spanish	OS: Win NT	Release Date: 01 Oct 1996
Operational Range:	01 Jan 1950 - 31 Dec 2049
Prerequisites:	None
Product Dependencies:	Windows NT4 Service Pack 4 (Internet Information Server 3)
Clock Dependencies:	Operating System clock
Last Updated:	21 Sep 1999
Product Details
How the product handles dates: Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Windows NT file system. Service Uses dates? Compliance Issues Date Algorithm HTTP Proxy Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. WinSock Proxy No None N/A SOCKS Proxy No None N/A Cache Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Logging Yes None Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.   Two-digit shortcut handling: Interpretation of 2-digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate proxy and firewall operation with Proxy Server, web server and browser by setting system clocks to years before equal to and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: English	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: French	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: German	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: Italian	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: Japanese	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: Latin America	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Proxy Server	Version: 2.0	Category:Compliant
Language: Spanish	OS: Win NT	Release Date: 17 Sep 1997
Operational Range:	-
Prerequisites:	None
Product Dependencies:	NT4-SP3, IIS3 or IIS4
Clock Dependencies:	operating system clock
Last Updated:	21 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Proxy Server 2.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. How the product handles dates: Microsoft Proxy Server uses dates to calculate cache expiration dates and to annotate logged entries. Users can not enter dates into any part of the Proxy Server product. Dates are extracted from HTTP headers and from the Microsoft Windows NT Server file system. Service    Uses Dates?    Compliance Issues    Date Algorithm HTTP Proxy    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      WinSock Proxy    No    None identified    N/A      SOCKS Proxy    No    None identified    N/A      Cache    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Logging    Yes    None identified    Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999.      Two-digit shortcut handling: Interpretation of 2 digit year is as follows: 0-49 is considered 2000 – 2049. 50-99 is considered 1950-1999. Testing guidelines and recommendations: No special testing should be required. Users may choose to simulate (on non-production systems) their proxy and firewall operation with Microsoft Proxy Server, web server, and browser by setting system clocks to years before, equal to, and post 2000.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Publisher 2000	Version: 9.0	Category:Compliant
Language: Chinese - Simplified	OS: 32-Bit Win	Release Date: 25 Mar 1999
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Microsoft Windows 95 operating system or later, Windows NT Workstation operating system version 4.0 or later
Clock Dependencies:	System Clock
Last Updated:	15 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Publisher 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. Operational Range for Data: System dependent How the product handles dates: The user can enter dates and time into a text or table frame as a field or as text. Publisher parses the system time to the display format selected by the user. Individual date/time field data does not contain date/time values, only formats. When creating a calendar via the calendar wizard, the user is prompted to enter a 4-digit year. 2-digit years are not accepted. Two-digit shortcut handling: The user can choose to display the date in a 2-digit format. The only conversion that takes place is parsing the system date to a 2-digit display format, which does not have an effect on the storage or manipulation of the date data. Publisher 2000 uses a number of Microsoft Office 2000 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 Publisher 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Publisher 2000	Version: 9.0	Category:Compliant
Language: Chinese - Traditional	OS: 32-Bit Win	Release Date: 25 Mar 1999
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Microsoft Windows 95 operating system or later, Windows NT Workstation operating system version 4.0 or later
Clock Dependencies:	System Clock
Last Updated:	15 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Publisher 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. Operational Range for Data: System dependent How the product handles dates: The user can enter dates and time into a text or table frame as a field or as text. Publisher parses the system time to the display format selected by the user. Individual date/time field data does not contain date/time values, only formats. When creating a calendar via the calendar wizard, the user is prompted to enter a 4-digit year. 2-digit years are not accepted. Two-digit shortcut handling: The user can choose to display the date in a 2-digit format. The only conversion that takes place is parsing the system date to a 2-digit display format, which does not have an effect on the storage or manipulation of the date data. Publisher 2000 uses a number of Microsoft Office 2000 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 Publisher 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Publisher 2000	Version: 9.0	Category:Compliant
Language: Croatian	OS: 32-Bit Win	Release Date: 25 Mar 1999
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Microsoft Windows 95 operating system or later, Windows NT Workstation operating system version 4.0 or later
Clock Dependencies:	System Clock
Last Updated:	15 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Publisher 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. Operational Range for Data: System dependent How the product handles dates: The user can enter dates and time into a text or table frame as a field or as text. Publisher parses the system time to the display format selected by the user. Individual date/time field data does not contain date/time values, only formats. When creating a calendar via the calendar wizard, the user is prompted to enter a 4-digit year. 2-digit years are not accepted. Two-digit shortcut handling: The user can choose to display the date in a 2-digit format. The only conversion that takes place is parsing the system date to a 2-digit display format, which does not have an effect on the storage or manipulation of the date data. Publisher 2000 uses a number of Microsoft Office 2000 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 Publisher 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Publisher 2000	Version: 9.0	Category:Compliant
Language: Czech	OS: 32-Bit Win	Release Date: 25 Mar 1999
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Microsoft Windows 95 operating system or later, Windows NT Workstation operating system version 4.0 or later
Clock Dependencies:	System Clock
Last Updated:	15 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Publisher 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. Operational Range for Data: System dependent How the product handles dates: The user can enter dates and time into a text or table frame as a field or as text. Publisher parses the system time to the display format selected by the user. Individual date/time field data does not contain date/time values, only formats. When creating a calendar via the calendar wizard, the user is prompted to enter a 4-digit year. 2-digit years are not accepted. Two-digit shortcut handling: The user can choose to display the date in a 2-digit format. The only conversion that takes place is parsing the system date to a 2-digit display format, which does not have an effect on the storage or manipulation of the date data. Publisher 2000 uses a number of Microsoft Office 2000 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 Publisher 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

Product Summary
Product: Publisher 2000	Version: 9.0	Category:Compliant
Language: Danish	OS: 32-Bit Win	Release Date: 25 Mar 1999
Operational Range:	-
Prerequisites:	none
Product Dependencies:	Microsoft Windows 95 operating system or later, Windows NT Workstation operating system version 4.0 or later
Clock Dependencies:	System Clock
Last Updated:	15 Sep 1999
Product Details
Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customers’ Year 2000 efforts, Microsoft intends to maintain Publisher 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade. Operational Range for Data: System dependent How the product handles dates: The user can enter dates and time into a text or table frame as a field or as text. Publisher parses the system time to the display format selected by the user. Individual date/time field data does not contain date/time values, only formats. When creating a calendar via the calendar wizard, the user is prompted to enter a 4-digit year. 2-digit years are not accepted. Two-digit shortcut handling: The user can choose to display the date in a 2-digit format. The only conversion that takes place is parsing the system date to a 2-digit display format, which does not have an effect on the storage or manipulation of the date data. Publisher 2000 uses a number of Microsoft Office 2000 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 Publisher 2000, please refer either to the document for the particular Office version that this application came with, or, in the case of a standalone product, to any version 2000 Microsoft Office document.

Legend of Symbols:
*	The product is compliant. User action is recommended, which may include loading a software update or assessing shared technology.
#	The product is compliant with an acceptable deviation 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 . Software updates are pending. Future maintenance actions will be recommended shortly.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.