Re: ODBC: Openlink, Intersolv or Informix?

[snip] > What bugs does 3.10 have? Like the 2.5 driver it can't do indexed reads. In VB for example this means you cannot use the update method of a recordset. You can still update via passthroughs, and this is normally preferable anyway, but it still does have the limitation. To my knowledge. > As an aside, we already ditched that pesky New Era (at my instigation). I stay up late at nights and pray for the demise of New Era. (We've got 2.12, yum). Luckily because we've just added SQL Server to the list of databases we write (duplicate) data too we may just be able to do this (get rid of it) as neither are flexible enough to control an environment satisfactorily. Should my manager grant my wishes for christmas, what route would you recommend to upgrading new era? My plan was to just rewrite most stuff in VB and something a little more powerful for any batch type processing. What might be nice would be an interim solution to distance ourselves from New Era What's the deal with this dyamic4gl? It may (or may not) be of use to know that our apps write to Informix (ODBC,Native), Fox and SQL Server (quad phase commit fucking hell) My tuppence J