RE: Problem with CURRENT function

This sounds like a bug to me. I'm running OnLine 6.10.UC1 under SCO 3.2.4.2. Just like your platform, mine isn't able to show better than 1 second resolution. But, all this means is that I always get .000 for the fractional part of datetime. (e.g., 1995-11-14 09:05:03.00000) Try running the statement: SELECT CURRENT YEAR TO FRACTION(3) FROM systables; from within isql. It should show you what the engine is returning. If it's junk, I'd say it's an engine bug. If it's good, then the problem is either a bug in 4GL or in the application. I don't know why this would have changed with an Informix upgrade. Did you by any chance upgrade your OS lately? --Craig (craig@chemistry.utah.edu) } } Recently we upgraded INFORMIX-4GL from 4.11.UC4 to 4.21.UE1. } After the upgrade we had a problems with the datetime variables created using } the CURRENT function. The problem is, it is inserting some junk values (like } 1995-01-01 08:01:00G). While analyzing the problem we found a release note } (see attached) which states that the CURRENT time is not supported any more } by the product. We are using a INFORMIX based application which uses the } CURRENT function and inserting datetime (year to fraction(3)) values to } different tables. Since we don't have thesource code, we cannot change the } application . We talked with INFORMIX support and they again refered to the } same } release note. When we asked what our options are (whether we have to live } with } older version of INFORMIX) , INFORMIX told us to degrade to the previous } version or not to use CURRENT function with fractions. We would like to } upgrade } INFORMIX to a later version like 7.0 or greater. Is the CURRENT function } supported with fractions in the new versions of INFORMIX (4GL)?. }