Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Uniqueness error
Message
De
09/06/1999 03:41:11
 
 
À
08/06/1999 16:48:43
Ronald Suen
Epic Solutions Inc.
Edmonton, Alberta, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00227676
Message ID:
00227789
Vues:
24
Ron,

Would !DELETED() slow down updateing of indexes?

Consider : have the Valid() code check for deleted records and RECALL them?




>>I'm having a heck of a time using a drop=down combo to add a new key if the entry is new or fetch it if it isn't. I get uniqueness errors from my primary index. Deleted records with the same item code that are hanging around are part of the problem some time. HOw do you handle the deleted records? It seems you should get rid of them as soon as possible but that means opening the table exclusively to PACK. One programmer said don't use primary indexes because of the headache and just control input at form-level. This seems a step backwards and self defeating to continue to learn and grow with vfp. This app will only be used by a couple of users and really only 1 at a time but I'm trying to make it multi-user ready. Thank you
>>John
>
>Try including ".NOT. DELETED()" as a filter in your index.
Kenneth.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform