Re: SQL code -246, ISAM code -154 problem.

P. Jennings wrote: }Running OnLine V5.0 under AIX. }We have a begin/commit process that locks a }parent record by updating a column with its }current contents. We find that if two users }try to update different rows in the same }child }table, the first will suceed and the other fail }with SQL code -246, ISAM code -154. }The two users are accessing different rows }in both the parent and the child tables. }This only happens if the first user has }not reached the 'commit' before the second }user trys to update. }Both the tables have row mode locking set. 1) You may also need to check the isolation mode around the select/cursor for the child tables. 2) How are the child records updated - if they use a "cursor for update" they may place locks on rows other than those ACTUALLY updated, which are only released at commit. If using explicit update statements using unique primary key they are more likely to succeed?