Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SET DELETED - more Command reference enhancement
Message
De
29/06/2002 16:22:20
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro Documentation de produit
Divers
Thread ID:
00673494
Message ID:
00673640
Vues:
23
>>Here's one idea, David:
>>
>>>Note: SET DELETED is ignored if the default scope for the command is the current record or you include a scope of a single record except in the case of the SEEK command, where SET DELETED is always respected.. INDEX and REINDEX always ignore SET DELETED and index all records in the table.
>>
>Hi Jim,
>
>It's incorrect and misleading because implies that SEEK commnad/function has a one record scope when in fact it doesn't. If you believe that such misconception exists, than help topic about SEEK command/function has to be revised. BTW, what do you think about INDEXSEEK() and KEYMATCH() functions.

Sergey,

Firstly, I *do* believe that SEEK is often/easily considered to have a scope of a single record:
1) SEEK has no standard VFP scope clause for good reason - the most you can ever get, and all you can ever get, is one SINGLE record. You can, of course, get none too.
2) SEEK will operate differently depending on the setting of DELETED, meaning that you cannot say that its 'scope' is the whole table. It's 'scope' is only the whole table when deleted is set OFF.
Mainly, though, the problem is one of interpretation of what is written in the Command reference entry at present. The intention of the documentation *may* have been to refer to VFP commands that HAVE scope clauses. But if this is the case, there is nothing distinguishing this and it is a far more sensible for any reader to infer the common English definition of "scope" than the specially-defined scope meant to limit specific commands' (English) scope.

As regards SEEK(), INDEXSEEK() and KEYMATCH(), there appear to be deficiencies in the documentation as relates to them too. I was limiting my comments (erroneously) to commands, excluding functions.
I get SEEK() and INDEXSEEK() respecting the setting of (SET) DELETED and I get KEYMATCH() ignoring it, always returning a .T. if a record exists regardless of its 'status' (active or deleted).
Consequently, I think that if these are your findings too then you should make a thread under this topic for each of those functions.

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

Click here to load this message in the networking platform