> Oh, that! All that is, is IB_SQL calling FETCH NEXT and there is no

NEXT

> because the cursor has reached the end of the set. That's the tool
> itself: the DSQL tab can only handle executable statements or select
> statements that return singletons (like SELECT MAX() or a select on
> rdb$database. So it performs a NEXT on the result to check that the

result

> is a singleton, and permits it if it gets that errorcode back. You can
> write exception handlers like that yourself...

Yes I do, but I don't surface them publicly! As a matter of fact it
was a dsql error, and getting returnvalues doesn't insure the call
din't leave a mess just waiting make your life miserable.....