Informix 7.2 Y2K Issue
I need some help solving a Y2K issue I have with Informix. Here's the situation: I wrote a front-end system in VB that queries, displays, and updates multiple tables in Informix. I am using an ODBC connection. On queries that update date fields in the db, I find that sending a date in the format '01/01/00' is saved in Informix as '01/01/1900'. I verified in ISQL this same problem using the identical update query. My DBA changed the environment variable DBCONFIG to 'F'. In ISQL, the problem disappeared. '01/01/00' was correctly interpretted as '01/01/2000'. But when I used my front-end system, it still came up as 1900. Does anyone have a suggestion other than changing my front-end to accept 4-digit years? Thank you, Bob Trenczer
In article <37838D56.2E57EDB8@vbws01.ba.ford.com>, rtrencze@vbws01.ba.ford.com wrote: > I need some help solving a Y2K issue I have with Informix. Here's the > situation: > > I wrote a front-end system in VB that queries, displays, and updates > multiple tables in Informix. I am using an ODBC connection. On queries > that update date fields in the db, I find that sending a date in the > format '01/01/00' is saved in Informix as '01/01/1900'. I verified in > ISQL this same problem using the identical update query. > > My DBA changed the environment variable DBCONFIG to 'F'. In ISQL, the > problem disappeared. '01/01/00' was correctly interpretted as > '01/01/2000'. But when I used my front-end system, it still came up as > 1900. > > Does anyone have a suggestion other than changing my front-end to accept > 4-digit years? > > Thank you, > Bob Trenczer > I think what your talking about is the DBCENTURY environment variable. There should be a corresponding environment variable that you can set through Informix's "setnet" utility. I'd set it the either "F" (Future) or "C" (Closest to current date). regards - kt Sent via Deja.com http://www.deja.com/ Share what you know. Learn what you don't.
Robert Trenczer wrote: > > I need some help solving a Y2K issue I have with Informix. Here's the > situation: > > I wrote a front-end system in VB that queries, displays, and updates > multiple tables in Informix. I am using an ODBC connection. On queries > that update date fields in the db, I find that sending a date in the > format '01/01/00' is saved in Informix as '01/01/1900'. I verified in > ISQL this same problem using the identical update query. > > My DBA changed the environment variable DBCONFIG to 'F'. In ISQL, the > problem disappeared. '01/01/00' was correctly interpretted as > '01/01/2000'. But when I used my front-end system, it still came up as > 1900. > > Does anyone have a suggestion other than changing my front-end to > accept 4-digit years? That's the best solution, by far. It's unambiguous. Failing that, you have to ensure that your environment with VB export DBCENTURY for you; the chances are, it currently doesn't. The other issue could be the version of ESQL/C (or ODBC) you are using with VB. You also make no mention of the database version, nor of any platforms. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.60 -- see http://www.perl.com/CPAN #include <disclaimer.h>