birding-aus Y2K bug in dBase III

This might also affect users of BirdInfo (which uses - used to
use? - a Clipper front end to dBase) and dBaseIV.

I handle my computerised bird records with an ancient dBaseIII
and have discovered a Y2K bug in my version of the software
which will give the year 1900 to some dates which you intend  to
refer to 2000.

If you set a date variable with a date this year (2000) and then
amend it by using a GET command followed by READ it changes the
date to one in the 1900s unless you have SET CENTURY ON.  So
amending '09/01/00' (created from today's date in 2000) to
'07/01/00' will give the date as '07/01/1900'.  But amending
'09/01/2000' works OK.

I've encountered quite a few other Y2K bugs in my programs but
all were due to my own coding and not the software.

Michael Norris





To unsubscribe from this list, please send a message to

Include ONLY "unsubscribe birding-aus" in the message body (without the
quotes)