Not only is this known, but even VFP 3 and 5 do the same thing and MS isn't planning on fixing them either.
This is basically due to the fact that the .DBF header where the last accessed date is kept, only has two characters to store the year. So without changing the .DBF structure (and making most every .DBF incompatible), it can't be "fixed".
Note: VFP 6, makes the assumption that if it's value is 00-79 (if memory serves) then it must be 20xx, so in ~78 years we'll have another "bad design" problem of major proportions <g>.
Rick