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

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. 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. 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? 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? Has anyone faced a similar problem??? Help appreciated.... Please post on the net or reply to smvaidya@auto.rockwell.com Thanks Sham Vaidya ------------------------------------------------ All opinions are mine and mine alone!!! ------------------------------------------------