>With this Hypothesis:
>"I must have an only result, independently from the fact that exists or an index does not exist".
>
>With this, if I have two various ones, sure there is an error.
>
>VFPT they had one apparently ambiguous choice ( for EXACT OFF this ambiguity is not introduced ).
>
>On first case, without index, LOOKUP search values using = comparison rule.
>
>On second case, with index, LOOKUP search values using seek comparison rule.
>
>But, because LOOKUP() it works also without indices,
>LOOKUP() like model is:

>LOCATE FOR SearchedField=eSearchExpression IN lookupTable && metacommand
>=ReturnField

>and therefore my choice falls on the first case:
>remove the ambiguity using the = comparison rule.
>
>I'm sure that you will contest this.

<*sigh*> Fabio, I'm not even sure what you just said, so how can I contest it?

In any case, I passed the report along, commenting it with various other results. It's in the hands of TPTB now...