>>>I sergey. what are the reasons for my table to corrupted. how did my table header got corrupted? is there a patch file for vfp 7. I don't have vfp 8 yet
>>>thanks in advance
>>
>>If MS could figure out how it get corrupted they would fix it by now.
>
>Sadly an accurate answer....

The fact that you may have 50, 100 or more database engines updating a single file on the network can be the answer. The foxpro database engine relies on the server to handle locks, to make updates and add records. If something goes wrong at ONE workstation, the table can become corrupted.

Microsoft's documentation states that "Under extreme conditions, some multiuser database applications that use a common data store over a network connection on a file server may experience transactional integrity issues or corruption of the database files and/or indexes stored on the server. This typically applies to some so-called "ISAM style", or "record oriented" multiuser database applications, not to a client/server relational system like SQL Server." and "A hazard of local caching is that written data only has as much integrity as the client itself for as long as the data is cached on the client. In general, locally cached data should be flushed to the server as soon as possible."

Check links:
http://support.microsoft.com/support/kb/articles/q129/2/02.asp
http://support.microsoft.com/support/kb/articles/q126/0/26.asp
http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

The issue is not just a VFP one, every application that uses shared multiuser acces to databases has issues with database corruption (Acces, Paradox, Codebase, Filemaker)

The answer can be a server component that handles at least locks and add/updates to tables and bypass the write cache(write synchronously), but I'm sure that we will never see this (even if is possible, CodeBase has one, and is used with DBFs).