>Hi Colin ---
>
>>I am USEing a free table and its IDX's, built back in the FoxPro 1.02 days, in a VFP app. The trouble I'm encountering is that VFP is setting some of the IDXs type to Candidate instead of Regular. How can I prevent this to ensure that the IDX's are opened as Regular? TIA
>
>I have not worked with FP 1 tables in VFP, but is it trying to convert IDX files to CDX tags? If so, are these UNIQUE indexes? Standalone indexes cannot be anything but regular or unique; they cannot be Candidates.

Hi John,

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?