Stellar Knowledge Base
When you try to export a table in MS Access 2000, the process may fail to display the following error message on your screen:
"The Microsoft Jet Database Engine could not find the Object. Make sure the object exists and that you spelled its name correctly"
If you click 'OK', you get another message on your screen:
"An error occurred trying to export the data from table tablename. The data was not exported"
You typically experience such behaviour, when the table that you are trying to export contains a self-join and Memo field. Additionally, you have applied referential integrity constraint on that table.
You should perform the following actions to resolve the error:
The above situation may also occur as a result of Access database corruption. In such circumstances, you need to take help of Stellar Repair for Access. It is an excellent tool that safely repairs corrupt MDB or ACCDB files to retrieve precious tables, queries, forms (with VBA code), reports, hyperlinks, OLE object fields, and other Access database objects. The software supports MS Access 2019, 2016, 2013, 2010, 2007, 2003, 2002, and 2000.
You need to follow the steps given below to recover your corrupt Access database using Stellar Repair for Access:
Stellar Repair for Access Stellar Repair for Access software fixes corrupt or damaged Microsoft Access files and saves the repaired database files to their default or a user-specified location.
Related Articles
WHY STELLAR® IS GLOBAL LEADER
0M+
Customers
0+
Years of Excellence
0+
R&D Engineers
0+
Countries
0+
PARTNERS
0+
Awards Received
Comment Reply
User Comments