>>>at least from 2.0. >> >>This goes back to dBase - the .dbf format has always had dates like >>this. Kind of thought of the problem 20+ years in advance. > >I know it was like that in dBase, but I never used FoxPro previous 2.0. :) > >Is there any database product that takes care of the Y10K problem? :) > >Vlad I've been testing a little - we get blank dates for years beyond 9999, but in datetime fields there's just enough room, because the date is stored as Julian day number as an integer (four bytes) plus number of milliseconds since midnight (another four bytes). So the problem is solved for the next milion years, just if we could persuade VFP to add some Set Millenium alongside with Set Century, and stop treating the values not between {01.01.100} and {31.12.9999} as erroneous. Anyone close enough to M$ to start lobbying on time?