This problem is usually due to a corrupted index in the database file and can usually be fixed by running the Repair Database Utility. It can also be caused by a newer version of the Microsoft Jet Engine being placed onto the system via Windows Update, mismatching Jet engines (some workstations have the latest Windows Updates installed and some do not), or some part of the Jet Engine has been uninstalled or removed. In any case, run the Repair Database from the File, Utility menu in Design Manager. To prevent and fix this problem, make sure of the following:
All workstations and the file server have the latest Windows Updates installed-- this will guarantee that all machines have the latest version (and the same version) of the Microsoft Jet 4.0 Data Engine.
Run a Repair database after Windows Update installs any updates to Windows. All users must be out of Design Manager to run a repair.
On systems with many active users (approx. 8 or more), schedule a repair to run once a week or even every day at night. This will keep the database compacted and in top working condition. To schedule repair yourself, use Windows Scheduler (usually on the server) to run repair.exe found in the Design Manager Directory. Run it with the /quiet switch to prevent it from prompting the user.
Re-run the client setup on the computer having the problem.