Damaged mdb file

A corrupted mdb file issues this message when I try to open it: "Microsoft has stopped the process because you and another user are trying to change the same data at the same time."The message is obviously wrong, no other user can be. I really want to restore this database because it contains client data. Please tell me how can I restore a file format Microsoft Access 2010 ?

To repair a corrupt .mdb database of MS Access, one can try Compact and Repair feature of MS Access. It repairs corrupt database and makes it accessible for database users. Other than this one can also use import feature of MS Access that helps database users import their corrupt database to a new database file.

also try to write a letter to the support service

or you can use recovery programs

The repair method attempts to recover only the tables, indexes and queries in the database. Do not attempt to repair damaged forms, reports, macros and modules. Before executing the Compact and Repair tool, please ensure the following condition:

1. Do not open Access database must closed
2. Sufficient storage space available - minimum double in size of your Access database on that Disk.
3. Close the .mdb file related to .ldb file before you delete the .ldb file.
4. Then Run the Compact and Repair tool

Try this sequence in order:
1. Backup.
Make a backup copy of the bad database, without overwriting any existing backups. Whatever has gone wrong, you don't want to make it worse, and a backup gives you multiple attempts at recovery.
2. Uncheck the Name AutoCorrect boxes.
In Access 2007: Office Button | Access Options | Current Database.
In previous versions: Tools | Options | General.
3. Compact.
In Access 2010: Compact and Repair Database on the Database Tools ribbon.
In Access 2007: Office Button | Manage | Compact/Repair.
In previous versions: Tools | Database Utilities | Compact/Repair.
4. Decompile.
Close Access, and enter something like this at the command prompt:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile "c:\MyPath\MyDatabase.mdb"
Use the path to where msaccess.exe is found on your computer, and include the quotes.
5. Compact again.
Open Access (holding down the Shift key if you have any startup code), and compact again.
Do this twice: one compact does not work in all versions (unless you close Access between step 4 and 5.)
6. Set minimal references.
Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access
7. Compile.
Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until the code compiles okay.
8. Set code options.
Still in the code window, choose Options on the Tools menu.
On the General tab, make sure Error Trapping is set to "Break on Unhandled Errors", and Compile On Demand is unchecked.
At this point, you should have a database where:
• the Name-AutoCorrect errors are gone,
• the indexes are repaired,
• inconsistencies between the text- and compiled-versions of the code are fixed,
• reference ambiguities are resolved,
• the code syntax is compilable, and
• the VBA options are set to show errors and avoid this kind of corruption.

Recovering from corruption
This article may help if your database is already corrupt
Before doing anything else, make a copy of the corrupted mdb file while Access is NOT running, and without overwriting any earlier backups. This lets you try different approaches and sequences if necessary.
Next, try the built-in repair utility. This very simple solution may work with corrupted indexes, and might even get rid of a corrupted object:
• In Access 2010, click Compact and Repair Database on the Database Tools ribbon.
• In Access 2007, click the Office button (top left), then Manage.
• In Access 95 - 2003, choose Database Utilities from the Tools menu.
If this does not work, follow the steps for the symptoms of your corruption below.

or you can use the recovery programs, there is a paid, but effective

mdb repair tool

Compact and Repair should work. Like many others have said, your best bet is to work on a COPY of the DB.

As to the original error, that most often happens on a single-user database when you have a form open to a given record, the form is marked with Me.AllowEdit = True, and you attempt to run any kind of SQL UPDATE action query while the form is open to any record that would have been affected by the query.