>Hi George ---
>
>>In a another thread, I mentioned that LUPDATE() wasn't Y2K compliant. After checking the Release Candidate of VFP 6.0, I'm pleased to let you know that in 6.0 it is.
>>
>>After setting my system clock to the year 2000, I modified a table in VFP 5.0. The value returned by ? YEAR(LUPDATE()) was 1900. However, in opening the same table (after having set my system clock back to 1998, ? YEAR(LUPDATE()) returned 2000.
>
>Hmmm....If the system clock is set to 2000 and you modify a table, LUPDATE() returns 1900? That's weird and a bit worrysome. What were your SET CENTURY ... ROLLOVER settings, if any?

Hi John,

Didn't set CENTURY or ROLLOVER in either case. I re-tested under VFP 6.0 and regardless of the setting of CENTURY (set to 18, 19, and 20) or ROLLOVER, the function always returned 2000 for YEAR(LUPDATE()). As a result, I don't think that the information is coming from the header anymore, but rather from the time stamp.

BTW, (and here's another piece of VFP 6.0 info), by default the settings for CENTURY and ROLLOVER are 19 and 48 respectively. I don't know if either are the result of the current system clock settings. I assume that CENTURY is, but I don't know if the ROLLOVER is calculated as 50 years lest than current or not. I'll test and repost. In 5.0, CENTURY is the same but ROLLOVER defaults to 0.