on 4/11/01 12:35 PM, David Cortright at [EMAIL PROTECTED] wrote: > If the OS can't handle dates past 2040, it make's no difference whether or > not any software running on that OS can handle it. IMHO. The *OS* can handle dates past 2040, the 'Date & Time' control panel stops at that date. I'm sure by 2040 Apple will have released an update to that control panel. The underlying OS and hardware can handle dates to 29,940 AD, and so can any application that uses the Macintosh Date & Time function calls. Why a particular MS apps doesn't, while not exceptionally surprising, certainly still is puzzling. Why reinvent the wheel? Harry -- To unsubscribe: <mailto:[EMAIL PROTECTED]> To search the archives: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
- Re: Year 2000/2038 compliance problem David Cortright
- Re: Year 2000/2038 compliance problem Paul Berkowitz
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem David Cortright
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem David Cortright
- Re: Year 2000/2038 compliance problem Michael W. Wellman
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem/What Ento... Harry (lists)
- Re: Year 2000/2038 compliance problem Harry (lists)
- Re: Year 2000/2038 compliance problem Harry (lists)
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem Christian M. M. Brady
- Re: Year 2000/2038 compliance problem Harry (lists)
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem Paul Berkowitz
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem Harry (lists)
- Re: Year 2000/2038 compliance problem Eric Hildum
- Re: Year 2000/2038 compliance problem D�nes Bogs�nyi
