FW: Anyone had any Y2K bugs yet?

Hi, I sent this email on Wednesday, and haven't had any replies yet. Has none else experieneced this? Dom: > Running informix 7.30.UC7 on HP-UX 10.20 > > run the following query from dbaccess or the in house application: > > > set isolation to dirty read; > SELECT cdredr_t, charge_start_dt, net_usg_b_type, serv_nature, > a_cat,b_tel_id,charge_dur, whole_ndisc_value, retail_disc_value, > int_rec_no, a_mob_id, serv_type,serv_code, serv_qual,a_equi_id, > rec_type, > usage_dur, tariff_class, charge_data_vol, non_charge_data FROM > sna_history_cdr WHERE a_tel_id = "0650800999" AND charge_start_dt >= > "2000-01-01 00:00:00" AND charge_start_dt <= "2000-02-23 23:59:59" > ORDER > BY charge_start_dt DESC> > From dbaccess, you see "isloation level set", and nothing else until you > do CTRL-C. The problem is the 1st date. Modifications to the date do not > stop the problem, unless you modify one of the 1st 2 numbers, i.e.: > > 2000-01 etc etc will not work no matter what numbers come after it, but > > > 2001-01 > > or > > 2000-02 will work. > > So it looks as if anything in the month of january 2000 is out. I don't > think that DBDATE or DBCENTURY would influence this. > > Any ideas? > > Dom