Thanks again Ed. You've been a great help.



>>Hey Guys,
>>
>>Thanks a lot! You've given me some alternatives to persue and I really appreciate it.
>>
>>Do you think if I copied Clipper files to VFP formats with the Codepage option that Clipper would be able to read them? Sure would save a lot of time & money if we could find some interim alternative until this legacy conversion is completed.
>>
>
>Clipper should be able to read tables from VFP as long as you don't use the extended file headers, so if you create the table from Clipper and don't modify the structure from inside VFP, you should be OK. If you create a table usnder VFP, you can always make a backwards-compatible copy of the data by doing a COPY TO ... TYPE FOX2X, the resulting free table will be a dBASE III/Fox 2.x style DBF, which Clipper can handle easily, and at least at one time there were RDDs available for Clipper that would let Clipper work with Fox 2.x style CDX files as well.
>
>You need to avoid data types that are not supported by Clipper in your shared tables, obviously; the same applies to using some of the Clipper-specific data types (Clipper could create character fields up to about 1K in size, which VFP doesn't support). If you don't use Fox-style IDX/CDX using a replaceable driver (RDD) in the Clipper application, you'll need to reindex the tables ujder Clipper if VFP adds/deletes records, or changes values of fields involved in Clipper indexes.