Since UFT must by defination cover many centuries, it must be Y2K compliant. What would happened to dates when 1599 changed to 1600 if the program was not compliant? The problems we face between 1999 and 2000 are the same as between 1599 and 1600.
Most problems with Y2K stem from the fact that a lot of programs only use the last 2 digits of the year and the program supplies the first two. This is fine as long as the first two digits are always the same, "19".
When the century changes so do the first two digits and the program can no longer decide what is correct.
Another problem is that every four years is a leap year. That is if the year is evenly divisable by four it is a leap year. But April fool, if the year is evenly divisable by 100, it is no longer a leap year except when it is evenly divisable by 400.
This means that 2000 IS a leap year, 1700, 1800 and 1900 were not but 1600 was a leap year.
I hope this is not too confusing but what it means is that if UFT can handle date changes from 1599 to 1600, it should be able to handle 1999 to 2000 the same way.