If you are lucky, USE MyCorruptedTable will raise an error.

Otherwise, you will need to open the table as a binary file and validate that the header is valid. About 99% of all corruptions are caused by a bad record count in the header. Or it could be the index file that is corrupted. Or it could be the memo file that is corrupted. Or it could be the database file that is corrupted...

Again, the amount of work required here to cover all the corruption causes and fix them will probably cost you more in term of time and money than buying Stonefield Database Toolkit.

>However, I still have the question, programatically, how do I determine that a table is corrupted? decisions will be made as to whether to continue processing or log the error and then continue to another table.
>I do not want to attemp further updates to the corrupted table, but what is the best and surest way to determine the table status?