SET CONTRAINTS and SET LOCK MODE

We are using a set contraints ... filtering without errors statement to facilitate fast deletes of records in a parent table, where child records exist. We set the constraints on the child table, after a violations table has been established for the parent. The strange thing is, that dispite the fact that we issue a set lock mode to wait 60 statement within the same transaction, we get the occational sql error -242, isam error 106 as soon as the set constraint statement has been issued. I can understand why the child table (or its parents) may have locks on it, but why will the set constraints statement return immediately and not wait 60 seconds for the lock to be released first? We do have DEADLOCK_TIMEOUT set to 60 in the onconfig. Any ideas? ps: we are running Online 7.13.uc1 on Solaris 2.5 -- +-----------------------------------------+ | Mark Christmas mchristmas@crosskeys.com | CrossKeys Systems Corp www.crosskeys.com | 350 Terry Fox Dr | Kanata, ON, Canada K2K 2W5 | Phone (613) 591-1600 Fax (613) 599-3626 +-----------------------------------------+