There is a way to repair ur damage database. Carefully read this before doing anything :
Before you run the Compact and Repair utility on a database, make sure of the following:
* Make sure that you have enough free storage space on your hard disk for both the original and the compacted versions of the Access database.
* Make sure that you have both Open/Run and Open Exclusive permissions for the Access database.
* Make sure that no user has the Access database open.
* Make sure that the Access database is not located on a read-only network share or has its file attribute set to Read-only.
Steps for trying to repair a damaged database:-
1. Make a copy of the damaged database (.mdb) file so that you have a backup.
2. Delete the .ldb file if it is present. You must close the corresponding .mdb file before you delete the .ldb file.
The .ldb file is used to determine which records are locked in a shared database and by whom. If a database is opened for shared use, the .ldb file is created with the same name as the corresponding database (.mdb). The .ldb file contains a list of users who have the database open.
3. Run the Compact and Repair utility. To do so, follow these steps:
1. If the database is open, close it.
2. On the Tools menu, point to Database Utilities, and then click Compact and Repair Database.
3. In the Database to Compact From dialog box, select the file that you want to compact, and then click Compact.
4. In the Compact Database Into dialog box, enter a new file name, and then click Save.
If the compact and repair does not succeed, you will receive a message stating so. This means the damage is so severe that it cannot be corrected.
4. If the previous steps fail to recover your damaged database, try creating a new database and importing the objects, one-by-one, from the old database to the new one. Then re-create the relationships. This technique resolves problems with damaged system tables in the database.
Note: You cannot import data access pages with the Import Wizard. Instead, open an existing data access page in the new database. To do so, follow these steps:
1. In the Database window, click Pages under Objects.
2. Click New.
3. In the New Data Access Page dialog box, click Existing Web page, and then click OK.
4. In the Locate Web Page window, browse to the location of the data access page.
5. If the damage is in a table, and the previous steps have not recovered the table, try the following:
1. In Microsoft Access, export the table to an ASCII (delimited text) file.
2. Delete any relationships associated with this table, and then delete the table from the database.
3. Compact the database.
4. Re-create the table and any relationships it had.
5. Using a word processor, examine the ASCII file for bad or strange data and remove those records. Save the file in an ASCII text file format.
6. Re-import the ASCII file into the newly re-created table.
7. Re-enter any records that you were forced to delete.
6. If the damage is in a form or a report, the damage can be either in the form or the report itself or in one or more controls on the form or the report. You can delete the form or report and import it from the backup copy of your database or use one of the following options:
* If the damage is in the form or report itself, create a new form or report, and then copy the controls from the original form or report.
* If the damage is in a control on the form or the report, create a new form or report, and then re-create the controls on the new form or report. It is best to re-create all the controls, because there is no way to tell which controls are damaged.
7. If the damage is in a macro or a module, the damage can be in the macro or the module itself or in the contents of the macro or the module. You can delete the macro or the module and import it from the backup copy of your database or use one of the following options:
* If the damage is in the macro or module itself, create a new macro or module, and then copy the contents of the original macro or module.
* The damage could involve non-ASCII characters embedded in the module. Save the module as a text file, remove any bad or strange data, and then reload the text file into a new module.
* If the damage is in the contents of the macro or module, you must create a new macro or module, and then re-create the contents of the original macro or module.
If you cannot repair the database with these steps, the database is probably damaged beyond repair. If this is the case, you should restore your last backup database or re-create the database.
As a final alternative, some consultants may provide a Microsoft Access database repair service.
Also I am providing for your future necessary steps to prevent databases :
* Avoid losing power during database writes. Losing power during database writes can cause the database to be left in a suspect state.
* Avoid dropping network connections.
* Avoid abnormal termination of Microsoft Jet connections such as power loss, manual shutdown, having Task Manager shutdown the application, and so on.
* When you are programming, close all DAO and ADO objects that you have open.
* Fatal system errors almost always cause abnormal termination. If your database is prone to fatal errors, you should resolve the errors before the database becomes too damaged to open or to recover.
* Compact the database often.
* Avoid a large number of open and close operations in a loop (more than 40,000 successive open and close operations could cause corruption).
Hope it will work for u.