For those clients who subscribe and continue to subscribe to a suitable FingerPost maintenance scheme past the millenium, FingerPost will fix any problem that occurs in their software as part of any such scheme with the exceptions described below.
We would like to point out that the average life of a file passing through a normal FingerPost installation can be measured in seconds while it is normally kept for a number of days. So the concept of a year is somewhat unnecessary and the millenium even more so.
Except for the database applications such as Soccer and Finance figures, we know of no FingerPost system which will be critically damaged by bad dates.
If you are unsure what systems will be affected where, FingerPost is willing to carry out an audit to confirm that we do not expect any problems on your particular site.
- FingerPost is totally reliant on the underlying operating system for date functions. If that system is NOT Y2K then FingerPost programs may not be too.
- Where a FingerPost program is used to manipulate data and a client chooses to be non-Y2K using sequences of Fip Parameters, there is nothing FingerPost can do to stop it. Examples of this include some of the data feeds to large library databases which only require a 2 digit year.
- Where input data is NOT Y2K, FingerPost system does NOT guarantee that the result will automatically Y2K. An example of this is the date/time stamp added on the end of IPTC 7901 and ANPA 1312 wire feeds.
- Where Third party software - Relational databases for example - are used that are NOT Y2K, then the data extracted may not be either.
- We are looking forward to a period of little work and big parties. Hope you are too.