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 2000 9.0 (French) - 32-Bit Win

Product Summary

Product: FrontPage 2000
Version: 9.0 Category: Compliant
Operating System: 32-Bit Win

Language: French Release Date: 25 Mar 1999

Operational Range: 01 Jan 1970 - 31 Dec 2036

Prerequisites: None

Product Dependencies: Windows 95, Windows 98 or Windows NT 4.0 (no specific Service Pack is required, however Service Pack 3 is recommended)

Clock Dependencies: System clock

Last Updated: 19 May 1999

Product Details

Product Maintenance: While Microsoft continues to recommend that customers install the most current Service Pack/Release for non-Year 2000 reasons, we understand that, for many reasons, this may not be possible. In order to aid our customersÆ Year 2000 efforts, Microsoft intends to maintain FrontPage 2000 version 9.0 as compliant through January 1, 2001. Newer Service Packs are also to be maintained as compliant, and may include additional non-Year 2000 updates. This is intended to minimize the Year 2000 as a reason to upgrade.

How the product handles dates:

Internally, FrontPageù

Stores, calculates, compares, and sequences dates in a 4-digit year format.
Is capable of using a 4-digit year format for user input and output.
Does not use special values for dates.
Handles dates more than 35 years beyond the year 2000.

Does not use a time/date stamp for license management.

Through the operating system, FrontPageù

Uses the system dates on the client executable.
Uses the system dates for server extensions, including UNIX.
Interpolates dates assuming the RFC1123 format.
Stores dates derived from the system in a 4-digit format and in 32-bit data structures. These dates are in a text formatùfor example, 26 Sep 1997 17:36:54 -0700.

. Front Page relies upon the operating system for leap year calculations.

On UNIX platforms, FrontPage uses the UNIX standard for dates. This means that FrontPage calculates the number of seconds from January 1, 1970. Using 32-bit data structures, the product has a date range through 2038, the same as all UNIX systems.

For file version and conflict detection, FrontPage relies on the date-time stamp (DTM). The DTM is created by using the system date.

At browse time, the Scheduled Include File and Include Scheduled Image FrontPage components use dates from the host HTTP server. The date edited and date last automatically updated values are determined as follows:

The "edited" date means the last time the document was manually updated.
The "automatically updated" date means the last time the document was regenerated by an action such as regeneration of a table of contents.

It is important to note the behavior of the Scheduled Include File and Scheduled Image components. Contrary to what some users expect, the files or images change only when the pageÆs dependencies are recalculated 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 recalculated when operations such as recalculate or check hyperlinks occur.

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







Two-digit shortcut handling: Not applicable

Common date usage errors:

The following notes on the behavior of FrontPage are not Year 2000 issues but relate to general date-time usage.

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 systems, the Era format is not used even though it is specified in the Windows Control Panel.
When using the Search component, the 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 as specified by the server system.
Users who do remote authoring across time zones should be aware of how the FrontPage components are designed to update when page dependencies are recalculated. Because 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:

In general, avoid testing in a production environment or with nonduplicated production files because side effects with non-compliant products cannot be predicted. Interoperability testing with other Microsoft Office products can be conducted safely.

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

Users should be aware that the TimeStamp value written to database tables as part of the "Form Results to Database" functionality is formatted according to the clientÆs selected system short date format. To ensure Year 2000 compliance, users should change their system short date format to display 4-digit years.

To change the system date format to display 4-digit years:

On the Windows Start menu, point to Settings, and then click Control Panel.
Double-click the Regional Settings icon, and then click the Date tab.
In the Short date style box, click a format that uses a 4-digit year (yyyy), and then click OK.

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.