RE: ESQL/C dtcvfmtasc()
You have DBCENTURY set to "C" - current. What is your system date? If it is today's date, then the function will fail, as 1900 is not a leap year. In order to accurately test this functionality, you must set your system date to some date after 12/31/99. Good luck! -----Original Message----- From: jlk62@aol.com32Qfree [mailto:jlk62@aol.com32Qfree] Sent: Thursday, October 07, 1999 9:22 AM To: informix-list@iiug.org Subject: Re: ESQL/C dtcvfmtasc() I'm reposting to make a correction to my original post (I accidentally put the date in as '99' instead of '00' - which has been pointed out by many a person on this list that 1999 is not a leap year, but 2000 is)! TIA ===== After having found that certain versions of Informix (both SE and IDS) don't support the leap year date (Feb 29, 2000), I upgraded IDS to version 7.30.UC2 (SCO Openserver 5.05). I can now see that the leap year date works. However, to insert a date/time doesn't - using the following: dtcvfmtasc("022900 000109", "%m%d%y %H%M%S", &date_time_varaible) fails. My version of ESQL is 7.22.UC2. DBCENTURY = 'C'. Any ideas? =====
William Raper wrote: > You have DBCENTURY set to "C" - current. C stands for Closest; R stands for pResent (and F for future and P for Past). -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.62 -- see http://www.perl.com/CPAN #include <disclaimer.h>