Problems with locks and committed read

Hi ! well, once again... another question on locks, and isolation level. This time it's rather "critical" for me. I've got 2 processes. One of them => insert data in some tables. The second => try to select row in it. (in fat , it select in it) the two transactions are initialized with => committed read, and lock mode to wait.and tables have row lock level. Everything works fine for insert, except that when i'm trying to read data with the second transactions .... it locks. In an ANSI DATABASE Dirty read will be a solution but i can't have phantom with this case .(data inserted are not "obligatorily" used so then can be removed before data selected is used in another transaction.) Well, this has been discussed often... But i still try my luck on this one .... Any idea ? I will studies any possibilites :) Change database mode, add query where needed. (is there a way with dirty read ON to see if a record is locked ??) By advance Thx ! Arnaud if you want to answer private: pubas 'A T' netcourrier com