Maintenance SQL Specific ASP Specific LSC Regs User Groups
Summary

 

Repairing a Corrupted Access Database

So you think your database is trashed, eh? Well, it may or may not be. The first thing to do is follow a few trouble-shooting steps. Depending on what we find, there will be different courses of action. So let's start at step one...

1) Is the problem happening on everyone's workstation? Go to two or three different workstations and try to re-create the problem. If you can re-create the problem, go to step 2 below. If not, or if it only happens on one or two workstations, the problem is probably with the database on the individual workstation. Standard fix:
a) Go to a workstation that works correctly. Make sure Clients for Windows is closed, then copy the CFW981.mdb from C:\CFW\ to a shared location on server.
b) Go back to the problem workstation and copy the CFW981.mdb from the server to C:\CFW981.mdb, replacing the existing file. If the standard fix does not work, try going to step 7.

2) Is the problem with a function in the program, or are you locked out of your database? If the problem seems to be with a function, go to step 4 below. If you are locked out, go to step 3.

3) Verify there is no one in Clients for Windows. It is possible that there is one workstation logged in and has the database locked. If this is the case, exit the program on that workstation, then re-enter the program. After logging in, proceed to the "Upkeep" tab. Once there, click on "Share Tables." You won't see any activity or messages and it does not hurt to hit the button more than once. Exit the program, then login again. Go to other workstations and try to login. If the problem continues, exit the program and open Microsoft Explorer. Now locate ClientsT981.mdb on the server. Go to top menu bar, click on "View," then "Folder Options," Now click on the "View" tab in the "Folder Options" window, then click on "Show all files." Finally click on "Ok." Go back to the location of the ClientsT981.mdb file and look for a ClientsT981.ldb file. If you find one, delete it. If neither of these has fixed your problem, proceed to step 4.

4) Compact (Click here for compacting instructions) your ClientsT981 database. There are two main methods for compacting the ClientsT981 database. However, they both start with verifying that there are NO users in Clients for Windows. Start with method one and if you get error messages, then try method two. Method one uses the standard compact utility built into Access 97/2000, while method two uses the JetComp utility. The JetComp utility is available from the Clients for Windows program CD, it can be downloaded from the Microsoft website, or it can be downloaded from the Kemp's Case Works website. If you receive an error message during compacting proceed to step 5. If compacting goes ok, but a function in the program still doesn't work, go to step 7.

5) When attempting to compact using method one, did it prompt you to repair the database? If yes, let it repair the database, then go back to step 4. If not, go to step 6.

6) Does the database appear to compact, then give you a "No read permissions" error message? If yes, proceed through the re-naming steps for compacting and try to use the compacted database. Sometimes the compact utilities will give the "No read permissions" error message as the compacting is completing, but it does not affect the usability of the compacted database. If this is not the error message you receive or the compacted database still doesn't work, proceed to step 10.

7) Do the computer(s) have Microsoft Access installed? If yes, re-apply latest service pack (Osr 1 for Office 2000 or Osr 2b for Office 97). Still not fixed, go to step 8. If no, go to step 9.

8) Uninstall Clients. Uninstall Access, or Microsoft Access as needed. Reinstall Access/Office choosing full install instead of typical install when option appears during install process. Install latest service pack (Osr 1 for Office 2000 or Osr 2b for Office 97). Reinstall Clients. Still not fixed? Go to step 10.

9) Uninstall Clients. Reinstall Clients. Still not fixed? Go to step 10.

10) Still not fixed? Unplug the server, carry it to the roof of your building ... then drop! Just kidding. If none of the above has helped, now would be the time to call Kemp's Case Works and speak to support.

 
Top of Page Home Previous Page

Copyright © 2002 All rights reserved Kemp's Case Works, Inc.

Home Customize Instructions Contact Category 5 Category 6 Category 7