CURRENT in triggers

We have found a problem in Informix 5.0 and 7.1 using CURRENT HOUR TO SECOND, or other precision specifiers within triggers. If the trigger is exported using dbschema (or such), it only shows up as CURRENT. This causes big problems if the exported trigger is re-installed if it refers to a non-DATETIME column. In some instances we use a CHAR(8) column, because we are in a heterogeneous database environment. Apparently, the trigger compiler is the culprit, stripping out the HOUR TO SECOND phrase before storing the ASCII representation of the trigger in the systrigbody table. The HOUR TO SECOND does get preserved in the trigger "object code", but the stored "source code" does not match the stored "object code". This is especially annoying, since the procedure compiler doesn't touch the procedure source code when it stores the text. Paul Kapp ----> PLKapp@aol.com -OR- plk@usorder.com