> The reason why I suggested it as the right one, is that SELECT SINGULAR
> returns either one row or no rows. You don't get an exception because, if
> the output evaluates to > 1 row, the SINGULAR requirement is not met, and
> you get no rows back at all.

When did they add in a SELECT SINGULAR syntax?

What I'm talking about has to do with which API call you use to execute the
statement. If you are using the TIB_DSQL then you use a different API call
than the TIB_Cursor uses. Which, when using it, implies a singular mode and
no cursor has to be created and you get an exception if 0 or more than one
record is returned.

Jason Wharton