Non-ANSI Informix databases and Intergraph

ANSI-mode Informix databases. Interesting things. There's no BEGIN WORK statement, and you must always specify the table owner as a part of its name. So given a million or so lines of code developed under Standard Engine and now running happily on both SE and non-ANSI Online systems there is little incentive to switch to ANSI mode. In fact there's a very good disincentive. Or at least there would be if the issue of interoperability hadn't just raised its mighty head. It seems that Intergraph's RIS product will only work with ANSI-mode Informix databases. Now don't ask me why; that's just the way it is (or so I am told by their locals). [Intergraph, are you listening? Email me please, I'd like to discuss this...] So we must now take a serious look at converting all this code to run on ANSI-mode databases if we want Intergraph to be able to access our databases. At least that's one option. A box of chocolate fish to anyone who can suggest a better one. And on a more general interoperability theme, are there any other advantages to be gained by using ANSI-mode databases? Are there perhaps more products like RIS which prefer this mode for some reason (and what would that reason be)? Sufficient strategic advantage would make the cost of code conversion somewhat more palatable. Thanks in advance... -- Hugh Grierson hugh@fujitsu.co.nz 16C, clear, cool southerlies