--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@i...>
wrote:

>
> At 10:40 PM 21/01/2006 +0000, you wrote:
> >--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@i...>
> >wrote:
> >
> > > SET TERM is an ISQL statement - it's not available (or needed)
> >outside the
> > > ISQL environment.
> > >
> > > Note too that, even if SET TERM were valid DSQL, ExecuteDirect
> >processes
> > > one and only one statement. Your complex CREATE TRIGGER or CREATE
> > > PROCEDURE statement is OK (its embedded statements are valid within
> >the DDL
> > > request) but adding extra statements is not. And if you are trying
> >to use
> > > ExecuteDirect to process an ISQL script, that can't work either.
> > >
> > > ./heLen
> > >
> >
> >Helen,
> > without the SET TERM i keep on experiencing errors like "SQL Server
> >Error-Token unknown, line 9 Char 1 END." It refuse the END keyword at
> >the end of CREATE TRIGGER statement. I've the same problem using an
> >TSQLDataset query.
> >Is it a dbExpress problem ?
>
> Could be. There is a Firebird driver available (www.upscene.com).

But for

> DDL statements I think you're supposed to use Execute, not

ExecuteDirect.

>
> However, for a reality check, make sure you don't have one END

statement

> too many.
>
> ./heLen
>

Helen,
using the Execute method of the TSQLConnection solved withot the
need of SET TERM.

Thank you

Alessandro