> This involves being able to recognize an EXECUTE BLOCK
> as well and get around the parameter parsing. At least, in
> a script, but possibly in a DSQL/Dataset descendant as well.

> People will want to use this, plain and simple. It also
> involves being able to return a resultl from INSERT INTO ...
> RETURNING statements and a decent way of displaying that. For
> example, via the .Params property, or via a single output row
> in TIBOQuery.

Is execute block intended to work in a script? What would be a
point without some script-based processing controls?

I am not entirely clear on the utility of execute block at this
stage, although I am sure it has some. Temporary/undeclared
stored procedures I guess is the intended purpose.

How easy or difficult will largely depend on how this is all
handled by the API. Have you tried it in a TIB_Cursor or
TIB_DSQL just to see what happens?

> Ahum, and then there's the "fbclient.dll" issue. Wasn't that
> your wrong doing? ;-)

Not holding grudges are we :-)


--
Geoff Worboys
Telesis Computing