Microsoft JET Database Engine error '80040e09'

You can use Recovery Toolbox for Access developed for recovering data from corrupted Microsoft Access databases. The MS Access recovery tool is capable of repairing MDB and ACCDB database files.

For more: https://access.recoverytoolbox.com/

You can use Recovery Toolbox for Access is used for recovering data from corrupted Microsoft Access database files with *.mdb, *.accdb extensions.

For more: https://recoverytoolbox.com/repair_access.html

First one apply short guide, second make use of http://www.mdb.openfiletool.com/ MDB Open File Tool
· Launch the Microsoft Access application, but do not try to open the corrupted MDB file.· Go to "Tools" in the top menu bar, expand the "Database Utilities" submenu and select the "Compact and Repair Database" option if you are using Access 2002 or 2003. If you are using Access 2007 or 2010, you can find the "Compact and Repair Database" option by clicking the Microsoft Office button and going to the "Manage" menu.· Highlight the MDB file that you want to restore and click the "Compact" button.· Enter a name for a new database file, which will contain the restored data from the damaged MDB file.· Navigate to the location on your hard drive where you want to save the restored version of the file.· Click the "Save" button. Access will now compact and repair the MDB file and save a restored version in the location you selected.

You say corrupt, in what way exactly? Do you get any specific error numbers/messages?

Have you tried Access repair program? Compact and Repair. If not, use it. But ensure that you made a backup, it is necessary because all the recovery tips can make the damage even worse.

Also try Jet Compact Utility. This tool created by Microsoft and it is much like Compact and Repair, but more successful in repairing.

If no one of above advice helps, then perhaps you need more powerful solution. In this case try to run a good third-party. I would recommend Recovery Toolbox for Access. It must help you. https://access.recoverytoolbox.com/

Have you tried creating a NEW MDB, and then IMPORTING the objects from the Crashed/Corrupted MDB?

This will SOMETIMES serve to rescue most if not all of the corrupted entities .

Or:
You can try:
eRepair Access is a powerful Access database recovery solution for damaged *.mdb and *.accdb files created in Access 2000 and above. Having such a tool at hand immediately after a database file corruption incident may save you a great deal of time, nerve and, of course, an ample amount of money that would otherwise be paid to third-party recovery services. With eRepair Access, you don't need to depend on anyone and entrust your Access data (often quite sensitive) into somebody else's hands. You don't have to wait. You don't have to call it a day knowing that the damaged Access file will not be restored (if at all) until tomorrow. With eRepair Access, you can be back in the game within minutes!

For more information: http://access.erepairtools.com/

If doesn't help, look here: http://www.filerepairforum.com/forum/microsoft/microsoft-aa/access/933-ms-access-database-recovery

You can try to use third party Access file recovery program to recover your lost and corrupted data from .mdb files. For more details about this software:-
Access File Recovery Software

error 3343 is a database error. Unfortunately, PCCharge is still in the stone-ages of computer technology and they think VB6.0 and MS Access 2.0 are stable and secure ... At any rate. 3343 is simply an unrecognizable database, in this case due to corruption. There is a program in the PCCharge directory called VisData. This will allow you to run a repair and compact the database. To use:
First make a backup of your PCCW.MDB database in your PCCharge directory (C:\Program Files\Active-Charge (PaymentServer); C:\Program
Files\PCCW (PRO)).

Execute VISDATA.exe.
File -> Repair MDB.
Select the PCCW.MDB database from your PCCharge directory.
Select 'No" to open Repaired Database.
File -> Compact MDB ... 2.0 MDB
Again, Select the PCCW.MDB
It will then prompt for what you want the database to be named. Simply select PCCW.MDB again, select 'YES' to replace existing database.
Select 'NO' to encrypt database.
Select 'NO' to Open Compacted database
Exit Visdata and start PCCharge.

It would also be a good idea to go ahead and update to the latest available Scripting Runtime library. This can be found by going to microsoft.com and searching for the phrase 'windows script'. (To my knowledge, 5.7 is the latest version).

When putting files up on your hosted site (or on your own server), make sure the file and the directory have the proper writes to Read/Write/Create. A special file called the .LDB file must be created and if it can't a ReadOnly status could be issued. It's a file that contains the names of the users currently accessing the MDB file. It stands for Lock Database. 
If you are running on Windows add these attributes, if it's linux (not sure why you'd use MDB on a LINUX box, but it would be chmod +777.

The way to get the database size is to point to the directory that the database is do a DIR statement with an output to a file as in DIR payroll.mdb>dbsize.txt and then read from the text file, the first field of the second line being the name (which you really don't need) then the size value of the database.

To import the text files using VB 8 use

'Imports System.Data.OleDb Dim conn As New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=d:\path\filename.mdb") Dim cmd As New OleDbCommand("SELECT * INTO [import] FROM [Text;Database=d:\path;Hdr=No].[dbsize.txt]", conn) conn.Open() cmd.ExecuteNonQuery() conn.Close()

see if the LDB file still exist and delete it...

Whenever you open an Access database, a file with the same name as the database and an extension of LDB will be opened automatically. For example if you open Northwind.mdb in the samples directory of your Access/Office installation, a file called Northwind.ldb will be generated. This new file keeps track of users and the objects that require some form of locking in the database. When all users have exited gracefully from the database, the LDB file is closed down and deleted.

thanks for rating