Re: Dates after year 2038
From: Stuart Toll (stuart.toll_at_online.nospam)
Date: 11/10/04
- Next message: John Ortt: "Re: Update and Append Query"
- Previous message: John Ortt: "Re: Update and Append Query"
- In reply to: Michel Walsh: "Re: Dates after year 2038"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Nov 2004 01:55:02 -0800
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.
"Michel Walsh" wrote:
> 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
>
>
> "Stuart Toll" <stuart.toll@online.nospam> wrote in message
> news:8C3ACD03-3527-461A-B5D1-5DDE680B432B@microsoft.com...
> > 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
>
>
>
- Next message: John Ortt: "Re: Update and Append Query"
- Previous message: John Ortt: "Re: Update and Append Query"
- In reply to: Michel Walsh: "Re: Dates after year 2038"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|