Re: ISOLATION!! VB-ODBC-INET-OnLine ISOLATION/Locking issue!!

I would test your application with the OpenLink ODBC driver before I did anything else. It can be freely downloaded from http://www.openlinksw.com Sham Vaidya wrote: :Hi, : :We are running OnLine version 7 on a UNIX box. I have clients accesing the :Informix Database from Visual Basic - ODBC - INET. We have an ANSI compliant :database. Do you *have* to have an ANSI compliant database? There are usually more problems than advantages. :Currently we are facing a problem where we are able to insert several :records in to a table, then perform a delete on one of the inserted records :and then a second delete thats when the problem occurs. The first delete :works fine, however the second delete has a problem and the error is that :the file is locked. I have row locks set on the table. Also after every :insert and the delete I commit the transaction. How do you do your inserts, deletes and commit? Show VB code. : I cannot get a handle why :the lock exists. Do I have an isolation problem? Is isolation set for a :every connection to the database (each session) or generically for all :the database for all connections? You *may* have a problem with VB connecting multiple times (separate connections) although I can't quite see that you should get the problem you do. :Also when VB connects upto OnLine the locks for systables, :sysusers etc. (5 system tables) are created and as a DBA if I try to give :connect permission to a user it tells me that the table sysusers is locked. :Anybody have any clue as to why this happens? No. :Has anyone faced a similar problem??? Help appreciated.... :Please post on the net or reply to smvaidya@auto.rockwell.com Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org