Hi John,

I decided just for my own curiosity to look at one of the IDX files as a hex dump and the before and after are different. If you, or anyone else knows what the different hex locations are for maybe this might shed some light.

Hex dump of IDX when coming up as Candidate in VFP:

00 02 00 00 FF FF FF FF 00 14 00 00 04 00 04 01
53 54 52 28 45 4D 50 4C 2C 34 29 00 00 00 00 00

Hex dump of IDX after recreating in FP2.5 DOS and coming up as Regular in VFP:

00 02 00 00 FF FF FF FF 00 0A 00 00 04 00 00 01
53 54 52 28 45 4D 50 4C 2C 34 29 00 00 00 00 00

The differences are in hex locations 9 and E.

>Hi Colin ----
>
>Glad it worked out for you....I still think it odd that IDXs can be tagged as Candidate. I thought that was impossible.
>
>
>>
>>Well, I corrected the problem but can only guess at the reason why the problem occurred. On a whim, I decided to delete the IDX's and then recreate them in FP2.5 DOS. Now when I USE the free table and the IDX's they come up as Regular. Thanx for the input.
>>
>>>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.