Quality problems caused by Informix bugs.

We are using Informix SE (5.01.UD1) and ESQL/C (5.01.UD2) on a DEC Alpha running OSF/1. Our version of ESQL/C has a bug in its ESQL pre-processor that causes it to generate error -33208 (Runtime error is possible because size of *host-variable-name* is unknown). We are told by Informix that although the warning is being generated, there is actually no problem and not to worry about it. Having said this, they won't fix it. This leaves us with a problem. We have gone to a lot of trouble to develop quality procedures according to AS3563 (Australian Standard) which is based on ISO9001 etc. At the time that we prepared our procedures we thought it entirely reasonable that we insist that our programmers develop code which would compile without errors or warnings using strict ANSI conformance checking compilers. We have been able to achieve this under OSF/1 (except Informix), HP-UX, Motorola System V R3, SCO Unix, LynxOS, VxWorks and OS-9. Informix is the problem. We are now in a position where we have to make a decision. Do we throw away Informix in favour of Oracle, Sybase, Ingres or something else? Are we being unreasonable in expecting Informix to fix the bug? I am interested in comments from Informix users about the standard of service they get from Informix. Do you have to fight your own quality procedures because of problems that suppliers like Informix give you? If you were to change from Informix, what would you choose? (I know the answer depends on the type of application, but if there are other database vendors which are better/worse at fixing bugs, I'd like to know). Please post replies to this new group if they are of general interest or email me otherwise. John Birrell CIMlogic Pty Ltd