This seems to problem with your network. And it can be dangerous because the files could become irreversibly corrupted...
Ask network administrator to check your network stability, lost packets, etc. You could also demonstrate the bug by creating simple network application which intensively reads/writes data to DBF similar to the one which is bocomming corrupted.
Main Topics
Browse All Topics





by: Olaf_DoschkePosted on 2009-06-30 at 08:48:06ID: 24746508
there is a setting TABLEVALIDATE, which might be set low when you restart, which will do less validation, perhaps even none. That way you may be able to process a table.
Even if that's not the case. The simply fact you sometimes get this error shows, there is some problem in the dbf, cdx or both. repair the table.
As you say it's not part of your database, I don't know now if its a database table at all or a free table. In case of a database table GENDBC.prg can help you build a healthy table with no data in it, to which you could append the data of the somewhat problematic dbf. For free table this tool is not an option. Give REINDEX a shot then, after making a backup.
Bye, Olaf.