I support an application that was written in VFP6, we have recently recompiled it in VFP8. There is a utility routine in the VFP application that rebuilds the indexes. There is another application that is written in Delphi, I think. It also uses a few of the tables from the VFP application. The Delphi app works fine if the index re-creation routine was ran in the VFP6-complied fersion, but will error out if the index was re-created in the VFP8-compiled application. I get an error message in the Delph app: Error 7017: Corrupt CDX/IDX index. If I manually delete and re-create the indexes with VFP6 the Delphi app still works, but if I manually delete and re-create the indexes with VFP8, the Delphi app reports the same error. This shows me that the error is NOT in the VFP app's code. I compared the actual cdx files using Beyond Compare, (which by the way, is a great utility) and it shows that the two cdx files (6 vs 8) are quite different.
I know that VFP is very backwards compatible, in fact Foxpro 2.6 for DOS can read the VFP8 index without a problem. Has anyone else experienced something similar to this? I have tried changing some of the SET commands (compatible, collate, etc.) prior ro re-creating the indexes also adding different keywords into the index on ... command, but to no avail.
I know that VFP is very backwards compatible, in fact Foxpro 2.6 for DOS can read the VFP8 index without a problem. Has anyone else experienced something similar to this? I have tried changing some of the SET commands (compatible, collate, etc.) prior ro re-creating the indexes also adding different keywords into the index on ... command, but to no avail.
