Microsoft TechNet - Year 2000



This static CD-based web site is representative of the www.microsoft.com/y2k site as of October 15, 1999.

Microsoft Year 2000 Readiness Disclosure & Resource Center

FrontPage Mac 1.0b (English) - Mac

Product Summary

Product: FrontPage Mac
Version: 1.0b Category: Compliant
Operating System: Mac

Language: English Release Date: 11 May 1998

Operational Range: -

Prerequisites: none

Product Dependencies: Mac OS 7.x; 8.x

Clock Dependencies: Operating System clock

Last Updated: 30 Apr 1999

Product Details

Operational Range for Data: 1970-1999

What are the prerequisites for compliance?

FrontPage Mac version 1.0 (b) (see below for download instructions)

To determine the version of FrontPage you are currently running:

Double-click on your hard drive
Open the System folder > open the Extensions folder > select the file FP Utility Library
Click on File > Get Info; look in the modified date of the file

Here are the dates you'll find for the different releases:

FP Utility Library Modified Date

FrontPage Mac 1.0 Fri, Feb. 7, 1997

FrontPage Mac 1.0 (a) Wed, Jan. 28, 1998

FrontPage Mac 1.0 (b) Mon, Apr. 20, 1998

If the version of FrontPage Mac currently running is less than FrontPage Mac 1.0 (b), then the below download is a prerequisite for Year 2000 compliance:

To download FrontPage Mac 1.0 (b), click on the hyperlink below and follow the instructions displayed:

http://www.microsoft.com/frontpage/mac/macupd.htm

This update may be installed on any version of FrontPage Mac 1.0.

Description of date handling.

FrontPage Mac 1.0(b) internally stores, calculates, compares and sequences dates in 4-digit format.
The user interface for input and output is capable of utilizing a 4-digit format.
FrontPage Mac 1.0(b) does not use special values for dates.
FrontPage Mac 1.0(b) will handle dates more than 35 years beyond the year 2000.
FrontPage Mac 1.0(b) does not utilize a time/date stamp for license management.

FrontPage uses the System dates in the following manner:

On client executables, FrontPage Editor and Explorer, FrontPage uses the operating system dates.

For Server Extensions, including UNIX, FrontPage uses the operating system dates.

All dates are interpolated assuming the RFC1123 format.

All dates are stored in 4 digit format

All dates in 32-bit data structures.

These dates are in a text format: e.g. 26 Sep 1997 17:36:54 û0700 and are derived from the system.

There are no leap year calculations inside FrontPage since the product leaves such calculations to the system

On UNIX platforms, FrontPage uses the UNIX standard for dates. This means it calculates the number of seconds from Jan 1 1970. Using 32 bit data structures, the product has a date range through 2038 like all Unix systems.

For file version and conflict detection we rely upon the date-time stamp (DTM). The DTM is created using the system's date.

At Browse time the Scheduled Include File and Include Scheduled Image FrontPage Components utilize dates from the host HTTP server. The date edited and date last automatically modified values are determined as follows. The "edited date" means the last time the document was explicitly manually updated. The Automatically updated" date means when the document was last regenerated by an action such as when a Table of Contents is re-generated.

It is important to note the behavior of the Schedule Include File and Schedule Image components. The files or images are changed only when the page's dependencies are re-calculated on the server. This means that browsing to a page does not cause the page to change if the time for a new image or file has passed. Dependencies are re-calculated when operations such as a re-calculate or check hyperlinks occur.

For example, these FrontPage Components will appear in the HTML as:







Does the product support 2 digit shortcuts for date representation?

No

What is the logic for converting 2-digit shortcuts to 4-digits for the storage and calculation?

N/A

Common Date Usage Issues

Here are some notes on FrontPageÆs behavior. These are not year 2000 issues. Rather these are general date-time usage issues.

FrontPage respects the localized date and time formats.

The TimeStamp components will preview the current time when in the editor and not the time last edited

For Far East System the Era format is not used even though it is specified in the Windows Control Panel

When using the Search component, the generated page that presents the results uses a single date format and not the format set on the host server.

When 24 hour time format is selected the TimeStamp component does not display the "AM/PM" format specified by the server system
For users who do remote authoring across time zones, users should be aware of how the FrontPage Components are designed to update when page dependencies are re-calculated. Since this is a server operation, the dates on the server are relevant and not the dates on the client's host machine.

Testing guidelines and recommendations:

For client-server environments testing should include cross time zone and time format data transfers.

Testing should also take into account that the Save Results form handler, via the "Additional information to save" section of the "Saved Fields" tab, allows users to specify whether or not they would like to save Time/Date information along with each submitted form record. If the user elects to save "Date", the date is saved internally in the 4-digit format but will display the form record in the MM/DD/YY format. Users who interpret this data will need this information. Users can instruct FrontPage 97 to output dates in the MM/DD/YYYY format. Information on how to do this is available at Knowledge Base Article Q214527

Return to Search Screen

Legend of Symbols:
*	The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
#	The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product.
+	The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

If after reviewing this information you have additional questions related to this product, click here.

YEAR 2000 READINESS DISCLOSURE

ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.

ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.

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.