Re: DBCENTURY Still gives wrong date

You have it wrong, there is no leap year for years evenly divided by 100 UNLESS they are evenly divided by 400, which 2000 is. YEAR 2000 IS A LEAP YEAR!! Please respond to rkirkwNo_Spam@mindspring.com To: informix-list @ rmy.emory.edu cc: (bcc: Kate Tomchik/IS/SSC/THD) Subject: Re: DBCENTURY Still gives wrong date I saw something like this on the Informix TechInfo web site. It said that the date 02/29/2000 returned an invalid date error code even with the DBCENTURY set properly. This is the correct response from the engine since leap years do not occur in years that are evenly divisible by 400 (or is it 200) even though it is evenly divisible by 4. Jean Appleton wrote in message <688hto$bm0@cssun.mathcs.emory.edu>... }Hello } }A while back there was a news message about a }date that was not handled properly by INFORMIX }even when DBCENTURY was set up correctly. I believe }it was a leap year and it was definitely in or after the }year 2000. } }I've misplaced the orignal post and need to supply the date }to my INFORMIX reseller. If someone has a copy of the }original message or knows the date in question would they }please send me a copy of it. } }Thank you } }Jean }