Thanks for the great advice.

>I have two approaches.
>
>1. IF the DBC is stable and not going to change I include it in the EXE. I've done this on two projects and they never had a problem.
>
>2. If (1) isn't appropriate I first try to overwrite the DBC with a good copy. I always keep "Before and After" ZIP files of the DBC/DCT/DCX files when making a DBC change. This would be in addition to your hospital-run backup. Finally I USE the DBC as a table, PACK it and then see if I can pick out any obvious problems visually.
>
>After that, it's pray that the SysAdmin did his/her job correctly. My last contract backs up regularly on tape - but has never been able to restore a single file. We did our own data backups to CDs weekly.
>
>HTH
>Barbara
>
>
>
>
>>What is recommended for quickly repairing a database container that has become corrupt? Granted, this has only happened to me twice in 4 years, it still is a mad panic.
>>
>>What I do if I can't validate a database or seem to repair it:
>>
>>1) Free all tables
>>2) Delete database container
>>3) Create a new database container
>>4) Add tables back into database
>>5) Recreate views (done visually)
>>6) Add in stored procedures
>>7) Lengthen any long field names that have been shortened.
>>
>>Is there a faster way to do this? Can take 30 minutes to an hour to do all of this. Restoring the database container from a tape backup might take 2 to 3 hours since backups are done centrally at the hospital. By the time the Help Desk calls and analyst and they find the tape...
>>
>>What does everyone else do to speed up the repair/recreate process?