Table troubles?, Here's your fix Options

[Tony Clifton]

If you have used Paradox for any length of time then you are probably familiar with the messages "Index out of date" or "BLOB has been modified" staring you in the face. If not, you will be soon enough. Paradox is not the most fault tolerant method for storing data, which is actually being kind. In truth, any interruption on your computer or network will likely cause the tables to crash. That's because Paradox opens tables and writes to them directly rather than doing it in segments. When an open table is not shut down in the manner it expects then it can't make sense of where anything is any longer. NexusDB, SQL Server and Oracle all protect their tables differently and are more resilient to any interruptions to its connection. Those could include a simple pause in your network connection, your computer going into stand-by mode, a crash of Windows or any other sort of break in the connection to the tables.

The good news is that your Paradox tables can nearly always be fixed when they get damaged. Read the documentation for repairing tables here and you will be back up and running.