Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Free table IDX interpreted as Candidate - How to prevent
Message
De
10/08/1998 14:15:27
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00125270
Message ID:
00125354
Vues:
9
Hi Colin ---

>
>The IDX files are not converting to CDX tags as far as I can tell. There is no CDX associated with the table. I also checked the indices using FP2.5 DOS and they are not set unique. One thought I've had is that even though the IDX is not set to UNIQUE the records being indexed are. For example, one IDX is indexed on STR(Empl,4) which is a unique code for each employee. At this time there is only one record per employee in this file so based on the record set the index appears UNIQUE even though it is not set this way. I'm wondering if this is causing VFP to interprit it as a Candidate. I need to prevent this because now multiple records per employee need to be added and this violates the Candidate key. Any thoughts?

What blows me away about your situation is that IDX files cannot be Candidate keys. No how, no way. What is telling you that it is a Candidate? Can you email me (jkoziol@asd-web.com) the tables/indexes and I'll try 'em out here?
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform