TimeWise logo

 [Timewise for Windows TimeWise for Windows |Timewise for Mac TimeWise for MacintoshTimewise for Dos TimeWise for DOS ]

Year 2000 Readiness Disclosure

Computer systems that cannot correctly process dates beyond 2000 are at risk of failure one second after midnight on December 31, 1999.

The good news is that all current releases of TimeWise for Windows, TimeWise for Macintosh, and TimeWise for the Web are ready for the transition to the year 2000. In fact, they are ready to deal with dates up to the year 9,999.
 

What is the Year 2000 Problem Anyway?
Many computer systems use a two-digit date format (such as mm/dd/yy), and experts believe that these systems could interpret the Year 2000 (00) as 1900.

This means that mission-critical information systems—and the institutions that depend on them—could be severely compromised by the turn of the century; everything from financial records to hotel reservations would be affected. This scenario of information meltdown has been called the Year 2000 problem, or Y2K.

The Y2K problem can come from several sources, including:

In addition, some systems may not recognize that the Year 2000 is a leap year. If a year is evenly divisible by 4, it is a leap year, unless it is also evenly divisible by 100. But if a year is also evenly divisible by 400, it is a leap year. So 1900 was not a leap year, but 2000 is.
 

TimeWise Year 2000 Compliance Statement

A Year 2000 Compliant* product from David Berman Developments will not produce errors processing date data in connection with the year change from December 31, 1999, to January 1, 2000, when used with accurate date data in accordance with its documentation, provided all other products (e.g., other operating system software, firmware and hardware) used with it properly exchange date data with the David Berman Developments product. A Year 2000 Compliant product from David Berman Developments Inc will recognize the Year 2000 as a leap year.

The TimeWise Year 2000 Compliance Statement refers to all TimeWise software products as originally delivered by David Berman Developments indicated as compliant on this website. The Compliance Statement does not apply to product features that have been customized or altered, or third party add-on features or products, including items such as macros and custom programming and formatting features. Only currently-supported TimeWise products have been tested for compliance. The TimeWise Year 2000 Compliance Statement and related Year 2000 information does not constitute a warranty or extend the terms of any existing warranty. The limited warranties provided for David Berman Developments’ products, if any, are set forth in the documentation and license agreements that accompany the products.

All information available from David Berman Developments concerning the Year 2000 is provided for the sole purpose of assisting our customers in their planning for the transition to the Year 2000.

David Berman Developments is continuing its efforts to make the Year 2000 information contained herein, as well as the information contained in its web sites and other communications, as accurate and up-to-date as possible; however, all Year 2000 information is provided without warranty.

Customers are encouraged to properly test their computer systems and related software to ensure that they have adequately addressed their Year 2000 issues.
 

*Definition of Year 2000 Compliance

We subscribe to this popular definition of Year 2000 compliance...

Year 2000 compliance means that software resources meet the following criteria and/or perform as follows:

Software to be used prior to, during, and after the  calender year 2000 will operate without error relating to date data. This includes, but is not limited to, date data century indication and recognition, sorts are correct, data entry will accommodate century where appropriate and calculations are correct that accommodate same century and multi-century formulas.

Software will not abnormally end or provide invalid or incorrect results due to date data, especially between centuries.

All calculations and logic of time-related data (dates, duration, days of week, etc.) will produce the expected results for all valid date values with the applications. Calculations and logic include sort algorithms, calender generation, event recognition, and all  processing actions that use or produce date values.

Date elements represented without century are unambiguous for all manipulations involving those elements.

The meaning of dates presented in reports and screens are unambiguous.


Timewise for WindowsTimeWise for Windows

All data stored in any version of TimeWise for Windows is Year 2000 compliant.
However, only TimeWise for Windows version 6 or greater gives you an interface in which you can type four-digit years. If you are using TimeWise for Windows version 5 or earlier, you should upgrade to version 6 or greater at some point previous to January 1, 1999. Upgrading is easy and automatic and doesn't damage your existing data in any way.

There is only one known anomaly in our current interface. This anomaly in no way affects the integrity of data or the utility of the product. The anomaly is that if you type only two digits in a four-digit year field, TimeWise will display a 19xx date rather than a 20xx date. The resulting date is typically inappropriate, and if so will immediately yield an error message because of its inappropriateness. Most TimeWise date fields suggest a year anyhow, so you rarely need to type all four digits... however, there are some cases where you will have to type all four digits rather than getting away with typing just two: a small inconvenience, but not a threat in any way to data integrity. We will likely publish a patch which will remedy this inconvience.



Timewise for MacTimeWise for Macintosh

All versions of TimeWise for Macintosh products are Year 2000 compliant.

There is only one known anomaly in our current interface. This anomaly in no way affects the integrity of data or the utility of the product. The anomaly is that if you type only two digits in a four-digit year field, TimeWise will display a 19xx date rather than a 20xx date. The resulting date is typically inappropriate, and if so will immediately yield an error message because of its inappropriateness. Most TimeWise date fields suggest a year anyhow, so you rarely need to type all four digits... however, there are some cases where you will have to type all four digits rather than getting away with typing just two: a small inconvenience, but not a threat in any way to data integrity. We will likely publish a patch which will remedy this inconvience.



Timewise for DosTimeWise for DOS

All data stored in any version of TimeWise for DOS is Year 2000 compliant.
However, we do not have plans to publish an interface for TimeWise for DOS in which you can type four-digit years.
Therefore, if you are using TimeWise for DOS, we recommend you migrate to TimeWise for Windows or TimeWise for Macintosh before January 1, 1999. Upgrading is easy and automatic and doesn't damage your existing data in any way.



[HOME]Back to TimeWise Home Page

Questions, comments, or problems? Contact info@timewise.net or fax (613) 482-4777.

Copyright © 1995-1999 David Berman Developments Inc. Certain names, logos, designs, titles, words or phrases on this page may constitute trademarks, servicemarks, or tradenames of other entities which may be registered in certain jurisdictions.

Updated December 2001