- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later.See Below | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
None | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | ||||||||||||||||||
none | ||||||||||||||||||
MS DOS Operating System 3.1 or later; or Windows Operating System 3.1 or later; or Windows for Workgroups 3.1 or later; or Windows for Pen Computing; or Windows NT Operating System 3.1 or later. | ||||||||||||||||||
Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. | ||||||||||||||||||
30 Apr 1999 | ||||||||||||||||||
Description of how the product handles dates: Microsoft PowerPoint stores all dates in a metacharacter placeholder that obtains and displays the current system time as a string when viewing in slide show or printing. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Opening Microsoft PowerPoint 95 or Microsoft PowerPoint 97 files in Microsoft PowerPoint 4 with the use of the import converters PP7TRANS.DLL (16 bit) and PP8TRANS.DLL will result in an incorrect date format. Presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". To work around this incorrect display, do not use 2-digit year formats when selecting 'update automatically'. Another workaround is to open the presentation in PowerPoint 95 or Microsoft PowerPoint 97 and resave it in the Microsoft PowerPoint 4 file format. For this method to work, you must replace the original PP7TRANS.DLL that shipped with Office 95 and Office 97 with, PP7TRANS.DLL version 7.07.1060 (for the U.S.). This download is available in both the PowerPoint 95 and PowerPoint 97 product guide. There is no fix currently available for the correcting the PowerPoint 4 installation. Common date usage errors: User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
|
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. |
- | |||||||||||||||||||||||
See below | |||||||||||||||||||||||
Microsoft Windows 95 | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
Operational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates in the 21st century when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060 (Note: Windows 95 and 98 users will see this file as 7.0), must be downloaded. Please see below for these downloads. Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Download PP7TRANS.DLL version 7.07.1060 http://microsoft.com/technet/topics/year2k/product/ppty2kus.exe
1. Download the patch to your desktop or to a specific directory such as c:\date Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/Articles/o95y2kinternational.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
System clock | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/Articles/o95y2kinternational.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this download please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties.
1. Download the patch to your desktop or to a specific directory such as c:\date Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/finland/downloadDetails/O95y2k.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
PP7TRANS.DLL version 7.07.1060 | |||||||||||||||||||||||
Microsoft Windows 95 | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
Operational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates in the 21st century when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060 (Note: Windows 95 and 98 users will see this file as 7.0), must be downloaded. Please see below for these downloads. Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Download PP7TRANS.DLL version 7.07.1060 To install the patch (For more information see the downloaded PP95 readme)1. Download the patch to your desktop or to a specific directory such as c:\date Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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.An Office 95 Year 2000 update is now available. For more detailed information and to download this update please go to http://www.microsoft.com/japan/Office/OfficeFreeStuff/Office/O95y2k/.Operational Range for Data: System dependent Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htm
Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
PP7TRANS.DLL version 7.07.1060 | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmOperational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates in the 21st century when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060, must be downloaded (Note: Windows 95 and 98 users will see this file as 7.0). Please see below for these downloads. Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Download PP7TRANS.DLL version 7.07.1060 FTP://ftp.microsoft.com/softlib/mslfiles/ppty2kus.exe
1. Download the patch to your desktop or to a specific directory such as c:\date Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/Brasil/downloadDetails/O95y2k.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/Brasil/downloadDetails/O95y2k.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
PP7TRANS.DLL version 7.07.1060 | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
Operating System clock | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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.An Office 95 Year 2000 software update will be available in June 1999 that will correct known Year 2000 related issues in the applications used in Office 95. For specific issues remediated by this software update see http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmOperational Range for Data: System dependentPrerequisites: For Microsoft PowerPoint 95 to execute short dates in the 21st century when saving to Microsoft PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060, must be downloaded (Note: Windows 95 and 98 users will see this file as 7.0). Please see below for these downloads. Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Download PP7TRANS.DLL version 7.07.1060 FTP://ftp.microsoft.com/softlib/mslfiles/ppty2kus.exe
1. Download the patch to your desktop or to a specific directory such as c:\date Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/articles/O95y2kfactsheet.htmClock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||
Office 95 Year 2000 Software Update | |||||||||||||||||||||||
Microsoft Windows 95; or Microsoft Windows NT 3.51 or later | |||||||||||||||||||||||
See Below | |||||||||||||||||||||||
21 Sep 1999 | |||||||||||||||||||||||
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 Office 95 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 An Office 95 Year 2000 update is now available that corrects all known Year 2000 related issues in the applications used in Office 95. For more detailed information and to download this update please go to http://officeupdate.microsoft.com/Articles/o95y2kinternational.htm.Clock Dependencies: Both operating system and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. Microsoft PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: Storage. Microsoft PowerPoint stores all dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. Microsoft PowerPoint calls the GetDateFormat system function to convert current date to a string according to the user-selected system settings.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations:
PowerPoint 95 uses a number of Microsoft Office 95 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 PowerPoint 95, 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 95 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||||||
PP7TRANS.DLL (version 7.07.1060) | |||||||||||||||||||||||||||
Microsoft Arabic Windows 95; Arabic Windows 98, or Arabic Windows NT Workstation 3.51 with SP 5 or greater; or Arabic Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | |||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||
18 Sep 1999 | |||||||||||||||||||||||||||
Operational Range for Data: System dependent
Clock Dependencies: Both OS and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates: For all Arabic 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 PowerPoint stores dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. PowerPoint 97 is calling the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function.2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors: Saving to non-native formats (including for example Microsoft PowerPoint 4.0) may cause loss or incorrect entry of century data for Insert Date and Time functionality. More specifically, presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". For Microsoft PowerPoint 97 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060 must be downloaded. User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document.
|
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. |
- | ||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||
See below | ||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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
Clock Dependencies: Both OS and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||
See below | ||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||
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 Office 97 Service Release 2 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.Prerequisites: Download a new version of the translator, PP7TRANS.DLL (version 7.07.1060), which is part of the Office 97 SR-2 Patch, available at http://officeupdate.microsoft.com/Articles/sr2fact.htm.The changes in Office 97 that were made in SR 2, including Y2K updates, are listed in http://support.microsoft.com/support/kb/articles/q151/0/20.asp. All Y2K issues reported as fixed in SR2 exist in SR1 and in the base Office 97 product.Clock Dependencies: Both OS and internal clocks are used. The internal clock is used only for time functions in slideshow rehearsal, animations and short delays. PowerPoint uses the Windows GetLocalTime call to get the current date and time from the system. Description of how the product handles dates:
2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors:
Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Other Issues (These problems are not specific to a century change, but may be exposed in testing for Year 2000 issues.):
PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See below | ||||||||||||||||||||||||||||||
25 Oct 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See below | ||||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
see below | ||||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 4 is recommended; SP4 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||
See Below | ||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||
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 Office 97 Service Release 2 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.
2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors: Saving to nonnative formats (including PowerPoint 4.0) may cause loss of or incorrect century data for Insert Date and Time functionality. More specifically, presentations created in PowerPoint 95 or PowerPoint 97 after 1999 with "update automatically" date formats that contain 2-digit years will be incorrectly displayed in PowerPoint 4.0 as a 2-digit year preceded by a "1." For PowerPoint 97 to properly execute short dates after 1999 when saving to PowerPoint 4.0 format, a new version of the translator, Pp7trans.dll version 7.07.1060, must be downloaded. The translator is available in Office 97 SR-2, which can be downloaded from http://officeupdate.microsoft.com/Articles/sr2fact.htm.
User applications should not rely on the text date representation within a PowerPoint presentation because it is only available as plain text. Query, calculations, and other operations are best conducted by using standard document properties.
In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify that dates are being properly used. The following table can be used to guide testing of PowerPoint within your organization.
PowerPoint 97 uses a number of Microsoft Office 97 shared files for the implementation of |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
18 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended] | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document.
|
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||||||||
PP7TRANS.DLL (version 7.07.1060) | |||||||||||||||||||||||||||||
Microsoft Hebrew Windows 95; Hebrew Windows 98, or Hebrew Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | |||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||
20 Sep 1999 | |||||||||||||||||||||||||||||
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 PowerPoint stores dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. PowerPoint 97 is calling the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function.2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors: Saving to non-native formats (including for example Microsoft PowerPoint 4.0) may cause loss or incorrect entry of century data for Insert Date and Time functionality. More specifically, presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". For Microsoft PowerPoint 97 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060 must be downloaded. User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 or the year 2000 software update in Office 97 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 and year 2000 software update 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.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | |||||||||||||||||||||||||||||
None | |||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended) | |||||||||||||||||||||||||||||
See below | |||||||||||||||||||||||||||||
05 Oct 1999 | |||||||||||||||||||||||||||||
Storage. Microsoft PowerPoint stores dates in string format or a metacharacter placeholder that obtains and displays the current system time as a string. PowerPoint 97 is calling the GetDateFormat system function to convert current date to a string according to the user-selected system settings. All date handling undergoes the same function. 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors: Saving to non-native formats (including for example Microsoft PowerPoint 4.0) may cause loss or incorrect entry of century data for Insert Date and Time functionality. More specifically, presentations created in Microsoft PowerPoint 95 or Microsoft PowerPoint 97 after 1999 with 'update automatically' date formats containing 2-digit years will be incorrectly displayed in PowerPoint 4 as a 2-digit year preceded by a "1". For Microsoft PowerPoint 97 to execute short dates in the 21st century properly when saving to PowerPoint 4.0 format, a new version of the translator, PP7TRANS.DLL version 7.07.1060 must be downloaded. User applications should not rely on the text date representation within a Microsoft PowerPoint presentation since it is only available as plain text. Query, calculations and other operations are best conducted using standard Document Properties. Testing guidelines and recommendations: The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft PowerPoint within your organization.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See Below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||||||||||||
Office 97 Service Release 2 | ||||||||||||||||||||||||||||||
Microsoft Windows 95; Windows 98, or Windows NT Workstation 3.51 with SP 5 or greater; or Windows NT 4 (no specific SP is required, though SP 2 is recommended; SP2 is required for Far East version of PP97 SR-1). | ||||||||||||||||||||||||||||||
See below | ||||||||||||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||||||||||||
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 Office 97 Service Release 2 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.
Microsoft PowerPoint 97 may change your date and time format when you insert a date to update automatically and then save the file to a PowerPoint 4 format. The date will still be correct, but it may be in a different format than the one selected. Example: the date 04-98 may be changed to Apr-98. PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||
PP8TRANS.DLL | ||||||||||||||||||||
Microsoft Thai Windows 95, Thai Windows 98, Thai Windows NT4(no specific SP is required) | ||||||||||||||||||||
see below | ||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||
Prerequisites: Download a new version of the translator, PP8TRANS.DLL available at http://officeupdate.microsoft.com/downloadDetails/pp8trans.htm in the PowerPoint download section.
Description of how the product handles dates: Saving to nonnative formats (including PowerPoint 4.0) may cause loss of or incorrect century data for Insert Date and Time functionality. More specifically, presentations created in PowerPoint 95 or PowerPoint 97 after 1999 with "update automatically" date formats that contain 2-digit years will be incorrectly displayed in PowerPoint 4.0 as a 2-digit year preceded by a "1." For PowerPoint 97 to properly execute short dates after 1999 when saving to PowerPoint 4.0 format, a new version of the translator, Pp8trans.dll, must be downloaded. The translator can be downloaded from http://officeupdate.microsoft.com/downloadDetails/pp8trans.htm.User applications should not rely on the text date representation within a PowerPoint presentation because it is only available as plain text. Query, calculations, and other operations are best conducted by using standard document properties. Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify that dates are being properly used. The following table can be used to guide testing of PowerPoint within your organization.
Other Issues. The following problems are not specific to a century change, but may be exposed when testing for Year 2000 issues.
PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document. |
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. |
- | ||||||||||||||||||||
PP8TRANS.DLL | ||||||||||||||||||||
Microsoft Vietnamese Windows 95. | ||||||||||||||||||||
See below | ||||||||||||||||||||
20 Sep 1999 | ||||||||||||||||||||
Prerequisites: Download a new version of the translator, PP8TRANS.DLL available at http://officeupdate.microsoft.com/downloadDetails/pp8trans.htm.
Description of how the product handles dates: 2-digit shortcut handling: Microsoft PowerPoint handles 2-digit dates for date field display only. User entry is text only and not considered a date representation. There is no conversion for user entry. Common date usage errors: Saving to nonnative formats (including PowerPoint 4.0) may cause loss of or incorrect century data for Insert Date and Time functionality. More specifically, presentations created in PowerPoint 95 or PowerPoint 97 after 1999 with "update automatically" date formats that contain 2-digit years will be incorrectly displayed in PowerPoint 4.0 as a 2-digit year preceded by a "1." For PowerPoint 97 to properly execute short dates after 1999 when saving to PowerPoint 4.0 format, a new version of the translator, Pp8trans.dll, must be downloaded. The translator can be downloaded from http://officeupdate.microsoft.com/downloadDetails/pp8trans.htm User applications should not rely on the text date representation within a PowerPoint presentation because it is only available as plain text. Query, calculations, and other operations are best conducted by using standard document properties. Testing guidelines and recommendations: In general, avoid testing in a production environment or with nonduplicated production files because side effects with other noncompliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be looked at to verify that dates are being properly used. The following table can be used to guide testing of PowerPoint within your organization.
Other Issues. The following problems are not specific to a century change, but may be exposed when testing for Year 2000 issues.
PowerPoint 97 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 PowerPoint 97, 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 97 Microsoft Office document.
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes)Danish ~ Engprj2a.exe (size: 97622 bytes)English ~ Frnprj2a.exe (size: 98445 bytes)French ~ Gerprj2a.exe (size: 98447 bytes)German ~ Itnprj2a.exe (size: 98164 bytes)Italian ~ Spnprj2a.exe (size: 98375 bytes)Spanish ~ Sweprj2a.exe (size: 98090 bytes)Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
None | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
none | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
none | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
none | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
PROJ2ACC.DLL | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: Project 4.0 Hebrew users need the following English files, which are available for download from the Microsoft Software Library: ~Engprj2a.exe (size: 97622 bytes) English After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
NOTE: You cannot mix languages. For example, if you have the English version of Microsoft Project, you cannot use the Spanish version of the Save to Database file contained in Spnprj2a.exe. Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
none | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||
For Microsoft Project 4.0 to use dates in the year 2000 properly when using the Save to Database functionality, a new version of the database file, PROJ2ACC.DLL must be downloaded. (see below for download information) | ||||||||||||||
Windows 3.1 or later, or Windows for Workgroups 3.1 or later, or Windows NT 3.1 or later. | ||||||||||||||
System Clock | ||||||||||||||
22 Sep 1999 | ||||||||||||||
Description of how the product handles dates:
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.
2-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
Instructions for Downloading the updated version of PROJ2ACC.DLL: The following files for your language version of Microsoft Project are available for download from the Microsoft Software Library: ~ Danprj2a.exe (size: 97860 bytes) Danish ~ Engprj2a.exe (size: 97622 bytes) English ~ Frnprj2a.exe (size: 98445 bytes) French ~ Gerprj2a.exe (size: 98447 bytes) German ~ Itnprj2a.exe (size: 98164 bytes) Italian ~ Spnprj2a.exe (size: 98375 bytes) Spanish ~ Sweprj2a.exe (size: 98090 bytes) Swedish After you obtain the file that matches your language version of Microsoft Project 4.0, do the following:
Warning! PROJ2ACC.DLL already exists. Overwrite (y/n)? Type "y" (without quotation marks) and click OK. Testing guidelines and recommendations: In general, avoid testing in a production environment because we cannot predict side effects with other products. Interoperability testing with other Microsoft Office products can be conducted safely. The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||
none | ||||||||||||
System 7 or later | ||||||||||||
System Clock | ||||||||||||
22 Sep 1999 | ||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling:
Common date usage errors:
Testing guidelines and recommendations:
The following areas should be examined to verify that dates are being properly used. The table below can be used to guide testing of Microsoft Project within your organization. Microsoft Project for Macintosh 4.0
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||
None | ||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||
System Clock | ||||||||||||||||
22 Sep 1999 | ||||||||||||||||
How the product handles dates:
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.
Two-digit shortcut handling: Conversion of 2-digit shortcut assumes a date window of 1984 through 2049. Common date usage errors:
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 95
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
none | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
none | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
none | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
None | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
NONE | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
none | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
01 Jan 1984 - 31 Dec 2049 | ||||||||||||||||||
none | ||||||||||||||||||
Windows 95, or Windows NT 3.51 with Service Pack 5 or greater, or Windows NT 4 with Service Pack 2 or greater | ||||||||||||||||||
System Clock | ||||||||||||||||||
13 Oct 1999 | ||||||||||||||||||
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.
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
|
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. |
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://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.
|
||
Wednesday, November 17, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act. |