Then your experience is totally different from mine. I have never had any problems when I have updated to a newer version of VFP, I repeat NEVER. In fact in the system I use in my own company every day, I have always used different versions of VFP on the same tables. And it was less than two years ago that I updated a backup program from FPD26 to VFP8.


>???
>There is not a single table i ever created in versions inferior to VFP7 that does work with VFP9. The only way is to use tablevalidate in order to open them. So, are ALL tables in FP2.5, VFP5-6-7 corrupted???
>It's true that if you open them in VFP9 with tablevalidate set to 0, then recreate them in VFP9, it will work in both versions no matter what tablevalidate setting you have in 9.
>
>Jaime
>
>>Wrong information, Jaime. SET TABLEVALIDATE to 0 is only necessary if you have some kind of corruption. And in that case you should fix the corruption, not simply ignore it.
>>
>>>In VFP9, just SET TABLEVALIDATE to 0
>>>Otherwise VFP9 won't open your table at all, and you can still keep on using it from previous VFP versions.
>>>
>>>Jaime
>>>
>>>>Hi,
>>>>
>>>>We want to write a small utility to update data in a VFP 6 table.
>>>>
>>>>However, we would prefer to write this utility in VFP 9 (it is likely to involve consuming data from a web service).
>>>>
>>>>Will opening the table in VFP 9 affect the structure of the table in any way?
>>>>
>>>>The database must still be useable by our VFP 6 application after it has been opened in VFP 9. Are we likely to have any problems?
>>>>
>>>>Regards.
>>>>
>>>>Matt.