Hi,

I'm awake now :-)

> >> > But more interesting, the error message is referring to line 257. I
> >> would be
> >> > looking at the prior statement(s) for a clue as to why this valid
> >> statement
> >> > is raigin an error.
>
> Actually, SET TERM is not a valid statement in DSQL, only in the isql

utility. What surprises me a bit is that Database Workbench is explicitly
parsing it as though it were a DSQL statement...the reason for my surprise
is that DBW uses IB Objects as its data interface and the IBO TIB_Script
component actually ignores SET TERM statements and DSQL terminators. It
also *knows* that semi-colons between the outermost BEGIN and END statements
in PSQL module definition statements are not DSQL terminators.

>

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

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

> So, maybe DBW uses its own custom method for executing scripts, that might

not have altogether caught up with the one-line comment convention
introduced in Fb 1.5.....

>

No no, Helen, it executes long scripts just fine.

> >> The prior statements are all comments. I little unusual, I
> >> know, but if you knew our generation process, you would understand.
> >>
> >> Steve Miller
> >
> >257 lines of comments?
>
> It could quite likely be a "challenge" to a script parser to locate the

first non-comment statement following a lengthy block of one-line comments
and/or a mixed bag of one-line and in-line comments. Do the comments in
your script use the "--" convention (one-line comments) or the "/*.....*/"
convention (in-line comments)?

>
> Helen

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com