>If you haven't got a recent backup, shame on you.

I have backups but it seems that the problem with the corrupted database was there for a while. You don't notice it until you do an open database with validate or if you try to add a new index tag. Just reindexing old ones seems to work.
>
>The .DBC/.DCT/.DCX are VFP tables; theoretically you could try out a file fix utility here on the UT. However, with something as important as a database container I wouldn't have any confidence in the results, even if it appeared to work.
>
>Basically, you're in deep doo-doo (that's a technical term :-)). You could create a new database. However, to add in your existing tables you'll need to first open them from VFP individually and break the existing links to the old, corrupted .DBC. This will kill all your relations, triggers, primary keys, long field names, etc. etc. You'll then have to re-establish them when you add the tables to the new .DBC.
How come : I create a brand new database (The original was created from a command file, not manually) with the same specifications. I verify...the database is valid. I copy the database container files over the broken one and it still fail. ?? But I will try the reverse (What you said). Copying the table into the new one instead.

>
>If you lost your .DBC due to a system freeze/crash, upgrade to NT/W2K (if you're not there already) and/or get your system tuned up. It never ceases to amaze me how many people put up with frequent system registry errors at startup, BSODs, general freezes, etc. Develop under those conditions and you're just asking for it.

It is already on NT for the server. The users are on Win98. This was caused by a network problem at the moment they was running a reindex procedure.