dbaccess/isql question

Lets say I have the following sql script (load.sql): begin work; lock table local_tbl in exclusive mode; delete from local_tbl; insert into local_tbl select * from otherdb:other_tbl where entry_date = TODAY;commit work; If I load this into dbaccess (or isql) and choose Run, and another process has a lock on an existing record in local_tbl, the lock table fails, and execution stops. The DELETE and INSERT statements will not execute if there is an error. If I try to run this directly (dbaccess dbname load.sql), every statement gets executed, regardless of the success of any prior statements. Is there any known way of controlling which behavior is used. I can think of instances where it would be desirable to support BOTH behaviors in both 'interactive' mode and 'batch' mode. Paul Kapp ----> PLKapp@aol.com -OR- plk@usorder.com