The information in this article applies to:
SYMPTOMSAfter Daylight Saving Time takes effect, the "Modified By" value in FrontPage Explorer is changed to reflect an inaccurate recording of the "Modified Time". CAUSEThis problem results when the server extensions recognize that the server's relationship to Greenwich Mean Time (GMT) has changed. This triggers a parse of all files in the Web to check for any date-related FrontPage components. This parsing is registered by the operating system as a modification of the file, even if no data in the file has changed. RESOLUTIONTo resolve this problem, install the latest version of the FrontPage 98 Server Extensions. STATUSMicrosoft has confirmed this to be a problem in Microsoft FrontPage 98 for Windows. This problem was fixed with the 3.0.2.1706 version of the FrontPage Server Extensions. MORE INFORMATION
This issue affects only Windows NT-based Web servers where Web content is
located on an NTFS partition. In this situation, following a change from
Standard Time to Daylight Saving Time (or vice versa), an incorrect
Modified Time is displayed in the FrontPage Explorer, and the Modified By
information is no longer available.
FrontPage Explorer shows 15:00 because looking at 14:00+0100 as a GMT would
indicate that the file was saved at 13:00 GMT instead of 12:00. Then the
client puts it back into its own local time zone, which is GMT+0100 plus
another hour for Daylight Saving Time.
The end result is (13 + 1 + 1) = 15:00. The Web is recalculated because, to the extensions, the time adjustment on the server represents a more recent edit than the last time the file(s) were edited by FrontPage. This recalculation is to account for the possibility that the user may not have used FrontPage to edit one of the HTML files. Because FrontPage has no information regarding who performed the most recent edit (it was the operating system that changed the date stamp), the Modified By value is discarded. This behavior did not occur in FrontPage 97 because FrontPage 97 recorded times in the local time zone of the server. This was fine as long as the client and server were both using the same operating system and in the same time zone; however, problems arose whenever the time zones or operating systems of the two sides of the network interaction were not identical. For more information about how Windows NT handles Daylight Saving Time, please see the following article in the Microsoft Knowledge Base: Q129574 Time Stamp Changes with Daylight Savings
Keywords : fp98 |
Last Reviewed: August 12, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |