Re: Patron Birthdate

[Sharon Wieczorek <swieczorek@xxxxxxxxxx>]

Hi Martha,

The reason the 2032 year is 'taking' is because of the year 2000 and the Y2K
solution put into place to correct the four digit year problem. Too bad they
couldn't put in a patch for the year 1932. Maybe the thinking for correcting date
problems is not "backward compatible." (Sorry, I just couldn't resist saying that.)

Sharon Wieczorek
Serials Supervisor
Mercyhurst College
Hammermill Library
Erie, PA 16546

Martha Driscoll wrote:

> We just turned on the patron birthdate field and have been in the process
> of moving the date that we stored in a note field into this fixed field.
> We noticed that everyone who was born in 1932 did not store the date,
> although you could type it in the field.  If you save the record and go
> back in, then the date is blank.
>
> The helpdesk says that the system can't store 1932 because '32' is the
> ASCII character for a blank.  Does anyone else think it strange that a
> database cannot store the year 1932?  I tried 2032 and that does store ok.
> What do the rest of you do with your 71-year-old patrons?
>
> --
> Martha Driscoll, Systems Manager
> North of Boston Library Exchange (NOBLE)
> driscoll@xxxxxxxxxx
> Ph: 978-777-8844  Fax: 978-750-8472
>
> --
> This message was distributed through the Innovative Users Group INNOPAC list
> Public replies:  INNOPAC@xxxxxxxxxx
> Update your subscription options: http://innopacusers.org/list/listinfo/innopac