We have a situation where we are "accidentallly" converting FoxPro 2.6a for Windows tables to VFP 6.0 when we run some code that zaps, indexes and appends into the FPW 2.6a tables. We do not understand what we've done and I thought there might be a listing ofthe thigns not to do to a FPW 2.6a table to prevent conversion to a VFP 6.0 table header. We have not modified the tables in any way.

Is it possible that our recreating indexes from a VFP program is altering the table header to become a VFP table?