Hi Gavin,

Tried the VALIDATE DATABASE command for the first time after reading your post. Very useful for the future. I need to spend more of my reading time in the VFP hacker's guide. Many useful commands that I've not experimented with yet.

It ends up that the table had a header corruption. I appended a blank record and deleted it and packed/reindexed the table. This fixed the table.

Thanks of your help,
Dave


>Hi David,
>
>Have you tried the VALIDATE DATABASE command, it may be what you're looking for.
>
>Hope this helps,
>Gavin.
>
>>Hi,
>>
>>I'm attempting to fix a database corruption for a client on an off-site basis. The problem started when they lost power in the middle of inputting a record. The initial issue was a corrupted index file on one table, which I repaired.
>>
>>However, it appears that another table is not allowing records to be added through their application interface. There is no error message or anything. It just doesn't add a record when its supposed to. I don't have their application on my computer, but they emailed me the table that appeared to be causing the problem. I was able to append new records through the VFP command window, and could not find any issue with the table.
>>
>>To make the issue more complex, their database has an extensive quantity of tables and they don't have access to their source code. Basically, I cannot visualize how the program updates tables and when, since I don't have the application nor the source code. I don't know if the table problem is the result of a corruption with that specific table, or the end result of something else failing (such as another table not being readable).
>>
>>My question is the following: Is there any kind of table corruption that only appears within an application but not outside of the application? For example, records can be appended to the table by entering the "APPEND BLANK" command in the VFP Command Window, but their application will no longer update the same table (no error messages though). I don't think the actual application is corrupted, since it worked for them with a sample database.
>>
>>Any ideas how to go about finding the problem? Could it be the DBC that is corrupted, and not the table? If there is a subtle table corruption, would creating a new table file and copying the data to it fix the problem? I was thinking of trying the "Copy To" command, but not sure if it would copy the corruption too. I can't afford any kind of repair kit at the moment, so I'm on my own trying to diagnose and fix this problem.
>>
>>Thanks for any help,
>>Dave