OPEN fails when active set includes a locked row

We ran an experiment here on both versions 5 and 7 online engines. Locked a row with one process and tried to update several rows with another process. We never even got to the update because the OPEN of the cursor failed when the engine realized that *one* of the rows was locked. Our ISOLATION LEVEL is set to COMMITTED READ so I'd expect the process to fail when we FETCHed the locked row, but the failure on an OPEN really threw me. Is this normal? Have you run across such a thing? Should it matter whether we are doing page level locking or row level locking? -- +------------------------------------------------------------------------+ | Bob Payne Internet: bobp@dev.dsc.dalsys.com | | Systems Engineer : bpayne@netcom.com | | Dallas Systems Corporation Voice: (214) 383-2238 | +------------------------------------------------------------------------+