lock table doesn't!

I've hit a problem with Online v7. I have a 4gl application that allows (some) users to shell out. If I select this option, run dbaccess and run the following sql : begin work lock table update blah blah... commit work Online seems to ignore the lock table and locks each row instead; onstat -k tells me this. If I run dbaccess directly and then runthe same sql, the table is locked as expected. Although onstat -u reports that my 4gl application and the dbaccess are two seperate sessions, shelling out seems to affect the way the Online hanldes the lock table. Can anyone shed any light as to why the lock table is seemingly ignored in the first example? Any help is much appreciated, Ian Gledhill ( Yorkshire, UK )