Alan wrote: >Besides, the way I figure it, I'll probably release a new >version of my apps sometime between now and 2031... So will all of us, but I'd rather be concentrating on adding and improving features than on revving database structures. The point is that many many hours of work, including work by Palm engineers working on the DateBook app and conduit (not to mention Puma, Franklin, and many others) will have to be spend dealing with this problem. Unfortunate and totally avoidable. Steve Patt President, Stevens Creek Software http://www.stevenscreek.com/pilot The home of... PalmPrint && UnDupe && AreaCoder && Handy Randy Athlete's Calculator && PocketTimer && SnailMailer On Hand && Take An Order! && many more
- RE: y2k bug inherent in DateType? Terry Carnes
- RE: y2k bug inherent in DateType? Fawcett, Mitch
- 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
