>Hi,
> I am currently converting clipper based application to visual foxpro 5.0 code. The clipper code USE RDD to create
>CDX index. However, when I use foxpro code to create the same index and open the DBF files, the old clipper application complain that the DBF files is corrupted and also cannot use the CDX index too.
>Therefore, I would like to know what can I do to ensure compatible of the index and DBF between clipper 5.2 and visual foxpro 5.0.
>Any suggestion or advise is very much appreciated. Thank you
>
>Best regards,
>Virusim

A Clipper 5.2 program CAN use a foxpro CDX index.

There are several rules you must follow in order to get Clipper 5.2 and Foxpro 5.0 to read and write to the same table.

The Foxpro table must be from version 2.6 or lower.

You cannot use a Foxpro Table that is part of a Foxpro .dbc (database) file.

Remove ALL indexes from the table so that the .dbf does NOT have an associated .cdx file.

Use a Free Table in Foxpro 5.0 and convert the Foxpro 5.0 table into a Foxpro 2.6 table by using the "COPY TO" command with the "TYPE fox2x" switch.

The way the index is built is also crucial.
Build the index using the INDEX command.
DO NOT build the index from the GUI within the TABLE DESIGNER dialog box.
When the index is built it the .CDX file should have the same name as the .DBF file and be in the same directory.(one with file extension .dbf the other with file extension .cdx)
To avoid erratic behaviour how the table "sees" the index is important.
When inside the TABLE DESIGNER dialog you should NOT SEE the created indexes under the INDEX tab.

In code you should get the table to "recognize" the indexes by using the command : SET ORDER TO [tagname} OF [CDXFileName]

With all of these conditions met a Clipper 5.2 program and a Foxpro 5.0 program should be able to access and modify the same .dbf file with no problems.

Hope this helps,
Dave.