>This is not a problem, it's just a matter of different defaults for the SET CENTURY TO setting. If you SET CENTURY TO 20, VFP will put that in front of 2 digit dates.

Not usually, though I'd still call it a bug :) However, I am faced with having a Y2K compliance auditor watching over my shoulder as I demonstrate vfp5 compliance. Therefore, to avoid potential problems I had to cheat a little and put:

SET CENT TO VAL(LEFT(ALLT(STR(YEAR(DATE()))), 2))

in my startup.prg. I didn't know about the little vfp5 bug when I submitted my Y2K docs, and said that vfp5 was compliant without SET CENTURY (whoops)...