Dates after year 2038

[Guest]

According to the knowledge base article at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;240246 some Jet 4
functions do not support dates after the year 2038. Does anyone have any
additional information about these limitations, specifically which SQL
commands it affects.

Thanks

 

[Michel Walsh]

Hi,


I am surprised by the article. 2038 sounds like a limitation on some
system that use long integers to store time in milliseconds since, if I
remember well, sometime close to 1970. That long integer would get an
overflow past 2038, and would turn in the negative. Furthermore, Jet 4.0 is
not aware of the Gregorian reform, so it should also be limited to year
1753, not back to year 200.


I try to get more details and post back if anything relevant about it.
but seems,

either the article is wrong
either Jet 4.0 untimely uses a C library where time is stored in
msec since 1970
either only "some" exportation functionalities are implied,not
internal working


Hoping it may help
Vanderghast, Access MVP

 

[Guest]

Thanks for your message. Please let me know if you find any additional
information otherwise I might have to raise a support call with MS.