Re: ODBC Driver problem

Tim Haynes wrote: > OpenLink (http://www.openlinksw.co.uk/) work well with VB and Informix. Have > a look around and download the free non-expiry evaluation drivers (ODBC and > JDBC). > > In article <6uo48n$qj9$1@starburst.uk.insnet.net>, > "John Clynes" <jclynes@family.co.uk> wrote: > > I am using Informix's CLI 2.5 ODBC driver (obtained from Online 7.23). > > However, it seems the driver is pretty limited. From VB I cannot edit a > > recordset using the edit or update methods. > > The error I am getting is that the object or database is read-only. > > > > I can work around this, but am a little suprised that the driver is so weak. > > Does anyone know of any better driver's knocking about? This OpenLink deluging is getting a bit much (2 postings from OpenLink on the same thread?). I have no objection in principle (cos I do it as well), but at least try to help out the poster instead of suggesting just try xyz driver. Funnily enough, the problem would probably affect the OpenLink driver as well. The problem, as another poster suggested, is probably because the table doesn't have a unique index on it, and VB is probably using the MS Jet, which likes a unique index on the table before it will update the table. Yes, we do have an ODBC driver (which will "work well with VB and Informix") and please try it (http://www.sco.com/vision/products/sqlretriever/), but I suspect a unique index may solve the problem! Allan Gould (allang at sco dot com) (Please remove anti-spam measures if replying)