Reindexing files without FoxPro software 2

[eyssel]

Hi, we have a very old application that uses Foxpro (not sure what version but I'm guessing 2.6 for Windows.
This morning the application gave an error stating there is a problem with the Index files and they need to be recreated. We do not have FoxPro software - is there any way I can pull the files (.Dbf and .Fpt?) into Access, try to rebuild the index and then paste it back to the application folder??? Is the .FPT files the index files for Foxpro?
If not I guess the only thing is to get an old copy of FoxPro and then reindex - where do I find the software?
Help will be greatly appreciated.
Thanks

 

[rajeevnandanmishra]

Hi eyssel,

FPT files are the files used with conjuction of DBF file. It stores the memo type data for respective dbf.
IDX and CDX files are the index files.

If it is a very old software then you must be facing problem because of IDX files.

I don't think if you can create indexes in Access for FoxPro.

Moreover, you can get Free version of FoxPro from any of the sites. But ofcourse you can search for it it companys nearer to you. Or, If if the data is not very confidential, you can send your dbf/fpt file to one of the foxpro 2.6 user. And tell them that on which fields you want to create the index. They can create it and send you back the dbf/fpt/idx files. (Unfortunately, currently i am not having foxpro for dos, otherwise i can recommend myself.)

 

[eyssel]

Thank you for the help. I will try and buy the software I guess that will be the best answer for the long run - and thanks for the tip about asking other users to help out with the reindexing.

 

[NathanGriffiths]

Hi Eyssel,

If its an old application, you should check the file sizes. There is a 2 Gigabyte size (2,000,000KB) limit for FoxPro files. fpt (memo) files can reach this size before the actual table does if the application accumulates data in these tables for historical purposes (e.g. an error log).
If the files reach this limit then you have to archive them or truncate them if possible.

Nathan

 

[BitFuzzy]

If this is in reguards to "index does not match table" statements. you could try deleting the index files ".cdx".
You'll need to know that the index's file name is though.

Also. plase a copy of the files in a different directory, incase it doesn't work. otherwise you "may" lose everything in your database

 

[eyssel]

Thanks for all the suggestions.
Finally we got hold of a person that used to support the application way back and it turns out there is a little backdoor built into the application by which you can get to a command line, and finally we did delete the .cdx file and could then reindex the table. So we survived this one - thanks again.