Re: ODBC Driver problem

I had the same problem, will be also interested if anybody knows what driv= er=20 to use=2E I'm using Informix CLI 7=2E20=2E I found a way around to send upd= ate SQL=20 statements directly to the server instead of updating a recordset, it shoul= d be=20 more efficient=2E you can also use stored procedures for any updates=2E william@carsinfo=2Ecom (William Harris) on 09/28/98 03:32:01 PM Please respond to william@carsinfo=2Ecom (William Harris)=20 To: informix-list@iiug=2Eorg cc: (bcc: Rafal Furdzik/PaulWeiss) Subject: Re: ODBC Driver problem Note: Some recipients have been dropped due to syntax errors=2E Please refer to the "$AdditionalHeaders" item for the complete headers=2E In article <6uo48n$qj9$1@starburst=2Euk=2Einsnet=2Enet>, jclynes@family=2Ec= o=2Euk says=2E=2E=2E >The error I am getting is that the object or database is read-only=2E > >I can work around this, but am a little suprised that the driver is so wea= k=2E >Does anyone know of any better driver's knocking about? Are you sure this isn't a result of the table definition itself? You can a= lso get that error if there is no primary index on the table=2E Primary/foreig= n keys might not work; the internal index names that Informix generates appea= r to be prefaced by a space, which confuses Visual Basic=2E -- William Harris william@carsinfo=2Ecom Check out the NAGS spam filter=2E http://www=2Enags=2Eorg __________________________________________________ This message is intended only for the use of the=20 Addressee and may contain information that is=20 PRIVILEGED and CONFIDENTIAL=2E If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited=2E If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately=2E Thank You=2E __________________________________________________