On Wed, 7 Apr 1999, Shaolin Hu wrote: > Don't you think it will be simpler just to raise the base year to say 1954. > Who need a date back to 1904 at year 2032? I have needed to do calculations on dates before 1930 for some historical research. Acutally Palm has just about the right time span for a 32 bit "number of seconds since" field. They should make it 64 bit in 4.0 - then they could adjust the base so I can go back into the dark ages, and still be able to say which day of the week a Star Trek episode is occuring on.
- RE: y2k bug inherent in DateType? Elia J. Freedman
- RE: y2k bug inherent in DateType? Aaron Ardiri
- RE: y2k bug inherent in DateType? Alan Johnson
- Re: y2k bug inherent in DateType? Chuck Christensen
- Re: y2k bug inherent in DateType? Steve Patt
- RE: y2k bug inherent in DateType? Shaolin Hu
- Re: y2k bug inherent in DateType? Marcel Guldemond
- Re: y2k bug inherent in DateType? Alan Pinstein
- Re: y2k bug inherent in DateType? Steve Patt
- Re: y2k bug inherent in DateType? Kenneth Albanowski
- RE: y2k bug inherent in DateType? Tom Zerucha
- RE: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? Aaron Ardiri
- y2k bug inherent in DateType? Michael Hutchens
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? krollin
- Re: y2k bug inherent in DateType? Michael S. Davis
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? Aaron Ardiri
- Re: y2k bug inherent in DateType? krollin
- Re: y2k bug inherent in DateType? Laurence Lundblade
