> Ummm....how do I answer this question? :-)
>
> I am saying that the script does stop executing (fails) at the point of the
> error. If autoddl is on or commits were called on previous statements, the
> previous statements would "stick"; but the failed statement and all after
> it would not be executed, i.e. the script stops executing. (I hope there
> are no single-double-triple negatives in that paragraph. <g>)

Try this script:

CREATE DATABASE 'c:\test.fdb' USER 'SYSDBA' PASSWORD 'masterkey';
CREATE TABLE T (i INTEGER);
INSERT INTO T VALUES (10);
/* Although this causes "arithmetic exception, numeric overflow, or string truncation" ... */
INSERT INTO T VALUES (10/0);
INSERT INTO T VALUES (20); /* ... this statement will be executed ... */
SELECT * FROM T; /* ... as you can verify by this SELECT, ... */
DROP DATABASE; /* ... and the database will be dropped here. */

So I would say that whole script does not stop executing,
only those commands that failed will ... errr... fail.

Should not I expect that not asking not umambuiguous questions is not good ? :-)

Ivan