MS Access database recovery steps:
1) Create a backup of the corrupt database. (Just in case of)
2) Create a new database and use File/Get external data/Import to get all objects of the damaged database.
3) Try these Microsoft solutions:
Repair A97/A2000:
http://support.microsoft.com/support/kb/articles/Q109/9/53.asp
Jetcomp:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q273956
and/or read the article:
ACC2000: How to Troubleshoot Corruption in a Microsoft Access Database
http://support.microsoft.com/default.aspx?scid=kb;en-us;306204
4) Bit "heavier":
Access decompile:
http://www.granite.ab.ca/access/decompile.htm
5) Try a recovery tool / Table rescue
Table datarecovery:
www.mvps.org/access/tables/tbl0018.htm
Access recovery:
http://www.officerecovery.com/access/index.htm
6) Ask a company (will cost $$'s ! )
http://www.pksolutions.com/services.htm
check also: http://www.granite.ab.ca/access/corruptmdbs.htm
All databases are heavy network users. To reduce the risk of corruption, these are things to do for any database:
1: Make sure your hardware is in top shape, all computers are routinely vacuumed to remove dust and lint and your network is set up correctly. Have all the machines on the same domain.
2: Have individual front ends on each machine. I created a database that checks the server for a newer copy of the front end, downloads it if needed, then runs it. You can get a copy of it at: http://www.nosuffering.com/Nelson/CheckForUpdatedFe.zip
3: Create a mapped drive for the backend or place the backend folder as close to the root folder and use only UNC path to the backend. Some people (and Microsoft) say the mapped drive is better, some say the UNC path is better. I have found it depends on the network setup.
4: Have the name of the backend and the name of the folders in the UNC path to it as short as possible meeting dos 8.3 naming specs and with only alpha numeric characters. \\server1\C:\db\db1_be.mdb is better than \\Database Server 601\C:\My Database Folder\Database Backends\My Database Backend_be.mdb
5: Don't run a local copy of the front end on the machine that has the backend -- best to have the backend on a server.
All of this is cutting down the number of times accesses need to be qualified, files need to be opened and closed and reduces the complexity of parsing the path all of which reduces the chance of corruption.
Nic;o)