Dear Customer: Red Hen Systems, Inc. has been asked to clarify its position on the Y2K bug. We have tested our software and remain confident that it will be unaffected by dates, prior to, during and after year 2000. If there is an instance where our software is impacted by the Y2K problem, we will make every effort to fix the problem promptly. In no instance would a Red Hen Systems software product cause problems with your mission critical operations. Red Hen Systems, Inc. has adopted the definition and standards described below as our working definition of compliance. It is the basis for our testing and the status information we provide. THE DEFINITION Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000. In particular: Rule 1: No value for current date will cause any interruption in operation. Rule 2: Date-based functionality must behave consistently for dates prior to, during and after year 2000. Rule 3: In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules. Rule 4: Year 2000 must be recognized as a leap year. If you are a MapInfo user, we would strongly suggest that you read their position, which can be obtained from their website (www.mapinfo.com). If you have any further questions, please feel free to contact me directly. Regards, Red Hen Systems Neil Havermale April 29, 1999 ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
