>>Hi!
>>I got an 'Index does not match table' error message when I tried to open my test database. To get around it I removed the .dcx file and issued a 'validate database recover' command. There were several objects in the container that were found corrupted and since my only choices were to delete or cancel, I chose 'delete'. The offending tables tat corresponded to these objects were removed but at least the database was recovered. I dread to see this happen for me in production. May I hear some wise advise from experienced users here? How does one painlessly work around this? Was there any other way that I could have recovered my database?
>>
>>TIA,
>>Evelyn
>
>- Backups, backups, backups
>
>- You can periodically run GENDBC, which creates a .PRG which, when run, can re-create your database from scratch.
In addition to that, there also an approach when each workstation has a local copy of the database which gets recreated from a PRG each time the user starts the application. If there are changes the latest copy of that PRG can be picked up from the server by the launcher program which runs the app. This way the user starts working with a brand-new database.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison