107 Error is solved

Firstly thanks to Jim Gordon, Kevin McHugh and Chris Wegener for posting me an answer.The problem was that the client made another typo error on the 2. script.He originally wrote: update test set text = "upd2" whereident_nr2 = 2 and ident_nr2= 2; This caused the optimizer not to use the index and do the sequential scan instead causing the 107 error. It will be for a psychoanalysis interesting to find the reasons which caused me to correct the statement (... where ident_nr1 = 2 and ident_nr2 = 2) in my posting, which of course didn't reproduce this error. However from this case I found out something useful (apart from reading the examples from the clients very very carefully -)).As Kevin McHugh pointed out there exists another reason for a 107 error apart from the already known (Table does page locking, no index on search kriteria, isolation level is set to Repeatable Read).The OPTCOMPIND Parameter should be 0 in the onconfig file. So again my apologies to everything for wasting their time, Regards Tolis Varnas tvarnas@orbit.de tvarnas@compulink.gr Location Xmas 95: Bonn, Germany