> First, make sure you execute the script in the Script Editor, this might
> sound
> obvious to you, but you wouldn't be the first.

Thanks for checking. I've never seen separate editors for a single SQL
and scripts before, and I'm not sure why they are separated. I am
using the SQL Script Editor.

> Indeed, the Script Editor uses TIB_Script and it should execute/use SET
> TERM just fine.

The 257 lines of comments have eight blocks of comments marked by /*
and */. Following those are about 137 carriage returns (hard returns),
for reasons I do not yet understand. Then more blocks of comments.

If I tell the concatenator to strip out comments, I am left with the
hard returns. The script runs past the SET TERM command. (...It runs
to another point where I am faced with a similar problem with SET TERM
.) If I leave the comments in, and manually take out the hard returns,
the script runs. Something about the combination of comments and
returns is giving me problems. Or it may simply be the length of the
comments, as Helen suggested. I don't know.

Steve