>Hi All,
>
>Often overlooked in our mad rush to make our older FP applications Y2K compliant is the fact that the PC BIOS may not be Y2K compliant. There are many quality apps out there that will fail on 1/1/2000 because the BIOS will start believing that its 1/1/1900. What to do? I've started wrapping all DATE() calls with a little program called Y2KDATE:

>
>FUNCTION Y2KDATE
>PARAMETERS dDate
>IF PARAMETERS() < 1
>   dDate=DATE()
>ENDIF
>IF dDate < {01/01/1980}
>   dDate = GOMONTH(dDate,1200)
>ENDIF
>RETURN dDate

>
>No PC BIOS will have a date before 1980, and if it does, adding 1200 months (not 100 years) to the system will fix it. The syntax for this is Y2KDATE(DATE()).

Hiya Gonz,

Just for any lurkers out there who don't know this, there is software available on the Internet for download that will allow you to test the BIOS for Y2K compliance. It'll test both the date rollover (from 12/31/1999 to 1/1/2000) and that 2/29/2000 is accounted for. I don't have the URL off-hand, but maybe someone can jump in.

In testing we did here, we didn't find a non-compliant machine that was a P200 or above. So mostly it was with the earlier Pentiums and (gasp) 486s. We also found that, even with a non-complaint machine, we could simply manually re-set the system clock and it would be ok and wouldn't require a daily reset (Feb. 29, 2000 excluded).