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.