Hi!

The same problem was 1 year ago here and it was with incorrect updating of the table header after transaction ends. When user than close application without correct data saving (crash, power off etc.), the table got corrupted. FLUSH command immediately after transaction helps here a lot (however, it do not helps with corruption at all, just make the less chanse for corruption).

In the files section here there are some fixing tools you can download. In addition, you can open table in design time in the browse window, add record manually using 'Ctrl+N', than delete it, than close. Here this fixed the problem. Note that table should not be in the buffering mode when you doing this. If this do not help, try to remove all indexes, do the same, than index table again.

HTH.

>I have a VFP 6 database that has been in use for 5 years. The application has worked fine until recently. The main table no longer allows new records to be added. Previous records can be modified, though. If I try to add a record, the form moves to the first record in the table and prevents me from displaying every other record. Exiting the application and reopening it will still only display the first record. Upon investigation, I noticed that if I open the main table in design mode and then sort on the primary index, a message is returned that the index is corrupted. After rebuilding the index, I can now browse the entire table and update existing records, but each time I try to add a new record, it corrupts the index and I am forced to rebuild it. The main table has 8530 records and the CDX file is 290 KB. I also noticed that if I open the table for read-only in Notepad, it looks like the new records are at the end of the file, even though they don't display when I browse
>the table. The application also use optimistic buffering.
>
>Any thoughts?