🚀 go-pugleaf

The documented base date is December 30, 1899.

Yeah, it's interesting to think about *when* there *would* be a
problem.  Since it's stored as a double, you need to think not only
about how *large* a number can be stored (about 1.80E308, according to
the docs), but *to what accuracy*.  Now, the mantissa has 52 bits, so we
could accurately represent:

 2^52 days = 2.50E15 days = 1.23E13 years (from the base date)

But what if we wanted accuracy to the second?

 2^52 seconds = 2.50E15 seconds ~ 143 million years (from the base date)

Let me know if I made a mistake!  If MS doesn't have this fixed in about
140 million years, I'm gonna start worrying...

Flewis wrote:
> 
> Access stores Date/Time fields as floating point numbers, with the date
> as the integer portion, and the time as the fractional portion. Dates are
> stored as the number of days from December 1, 1899 (I think). VB handles
> dates and times the same way.
> 
> Year 2000 compliance is actually a non-issue.... 
[cut]