>I dunno...
>After having this error, what can we do?
>I tried copying an old database container (DBC, DCT and DCX). Still the same message.
>Can I just recreate the database and copy the DBF files in the directory and then reindex and redo the view ?
>What should we do when this catastrophy append ?
>
>Thanks
>Eric

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

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.

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.