>>>>Thanks.
>>>>
>>>>I have tried these and they work ok. However,I would like to take advantage of the NTX files, if possible, to speed up access.
>>>
>>>Good luck...I tried something similar at the beginning of the year and finally just would recreate the indexes in FOX everytime I had to access the table. I looked hard and discussed it with many folks.
>>>
>>>Forget about using the NTX files...take a different route.
>>
>>If you write to a dbf that is also accessed by a Clipper program that uses the already set up NTX files then you will get an INDEX corruption error when the clipper program accesses the changed tables with an ntx index active.
>>
>>If you only read the dbf you can forget about using the NTX indexes.
>>
>>Further if you are writing to the table the dBase drivers provided by Microsoft will not update the NTX indexes.
>>
>>If that is your situation check out a company called "Intersolv".
>>They have drivers that modify Clipper ntx files as you write to the dbf in VFp or FPW. Check out www.intersolv.com . I would only use the drivers when you are writing to the table and another Clipper program MUST use the NTX files. That is the situation i am in with one of my clients. If anyone has a simpler solution for writing to tables indexed by NTX files and accessed by clipper programs i'd appreciate any input because the above solution is a real pain in the neck.
>>
>>The Intersolv ODBC driver are free to use for 30 days and then after that you can buy it for $99.
>>
>>If you could let me know how it goes i'd appreciate it Robert...
>>
>>HTH,
>>Dave
>
>What about using Clipper .CDX files? Is this suppported in the VFP ODBC's?
>
>Thanks

Yes Clipper programs can access .CDX indexes and in fact they can search using .CDX files just as quickly as Foxpro can. However, .CDX files are patented/copyrighted/"legal mumbo" FOX technology.

In my case i am dealing with a Clipper exe file that uses .NTX files so i do not have any options that way. But, thanks for the suggestion.

Dave