> > > and((:WHS='')or(WHS=:WHS))
> >
> >Why? - it works perfectly well in stored procedure code
>
> In stored procedure code, it *is* a variable. Don't be
> confused by the conventions. In Delphi, the :PARAM is the
> naming convention for replaceable parameters. In PSQL, it is
> the convention for signalling that you are referring to a variable.
>
> THEY ARE DIFFERENT USES OF THE SAME CONVENTION. AFAIR, there
> is an FAQ explaining this difference.
>

My point is that it shouldn't be different.
I'm guessing now . .
I assume IBO gets a list of parameters from the API which includes their
names.
It then presumably creates a structure for returning these with values.
When it processes a param assignment I assume it gives up after the first
occurrence of the param name ignoring any duplicates?
If this assumption is correct I would have thought it would be a great
improvement to get it to process any additional parameters with the same
name.

It also messes with the values turning '' into ' ' for a char(3). I
wonder what the justification for this is as FB seems happy to compare a
char(3) with ''?

Paul