>>>It is true that fp2.6 an VFP7.0 dbf's are different. Only in header Microsoft pu a few simbols that set with what product you work.
>>>My programmers tell me that if you open a DBF's with other version - it change header and could be not possible to open it with original one.
>>>We refuse that kind of project where client like to work simultaneously modules done with FPW2.6 and VFP7.0
>>
>>That's not entirely true. You can access and update fox2x table in VFP w/o converting them. However they'll be converted to VFP if you perform on them any command that requires exclusive use of table, like INDEX, PACK and so on.
>
>Nope, the only action that you can perform that'll deny Fox 2.x from opening a table that's been accessed via VFP is to add the table to a database. In fact, if a table has become corrupted in 2.x and cannot be opened with that version, opening and packing it in VFP often corrects the problem (usually connected to a bad record count in the header).

Just to add. After MODIFY STRUCTURE, INDEX, PACK or setting the code page of FP 2.6 table in VFP it still can be opened in 2.6.
However if you open FP 2.6 table in FP 2.5 and PACK it (when there are deleted records in the table) it will loose the code page info. But that's another story. :)