Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
PROBLEM: Optimized LOOKUP can get different values
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00827451
Message ID:
00827579
Vues:
28
Hi Garrett,

The answer is not immediate.

The error not derive from which of the two just or it is mistaken.
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.

But, even if the choice of the VFPT was corrected, not is trace of this in the documentation.

Fabio
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform