[Fixed] The Object was Saved in an Invalid Format and cannot be Read

                     [Fixed] The Object was Saved in an Invalid Format and cannot be Read

 Summary: You may encounter the error “The object was saved in an invalid format and cannot be read” in MS Access due to corruption in Access database files and many other reasons. In this post, you will learn the troubleshooting methods to fix this error. You’ll also get to know about a reliable Access repair tool that can repair the corrupt .ACCDB/.MDB files quickly and accurately. 

Many MS Access users reported facing “The object was saved in an invalid format and cannot be read” error in Access 2007 and 2016. However, the error can appear in other Microsoft Access versions as well. This error appears while opening, saving, or editing the forms and reports in Access, or exporting reports from Access to any other external sources. It usually occurs when MS Access fails to read the objects within the database. The objects can be forms, reports, queries, tables, etc.

Microsoft Access throws this error if it detects any issue with the database file. The reasons might be:

  • Corrupted objects within the database
  • Incompatible file format

Now, let’s see how to resolve this MS Access error.

Methods to Fix “The object was saved in an invalid format” Error in Access

You can start with the simple troubleshooting steps, like restarting your system or temporarily stopping your anti-virus software. If you are getting this error while modifying the reports within the database, then make sure you have all the desired permissions on the database. You can also try to open the reports in design mode. Sometimes, opening reports in the design view resolves the issue. If the error persists, then try the below methods.

Method 1: Change the File Format

The error “The object was saved in an invalid format and cannot be read” in MS Access can occur if the file you’re trying to open is not compatible with your MS Access version. For example, you’re opening an MDB file (default file format in MS Access version until 2007) in a latest version (2010 and later). In such a case, you can change the Access file format to a supportable format. Here are the steps to do so:

Method 2: Import Database Objects into a New Database and Recreate the Reports

Many users have confirmed that they’re able to fix the error by importing the database into a new empty database and then recreating the reports. Importing data from the damaged database file into a new file recreates the structure of the database file, including forms, reports, and other objects. Here’s how to do so:  

Method 3: Uninstall Windows Updates

Many Access users have reported encountering the error after installing the Windows updates. If this is also the case with you, then you can uninstall the updates by following the below steps:

In case the Compact and Repair utility fails to repair the database file, then the best option is to use a third-party Access repair tool to repair the corrupted database file. Raminfotech Repair for Access is one such tool that can easily repair severely corrupted database file. This tool can recover all the objects from corrupt database file, with complete integrity. This helps fix all the corruption-related errors. The tool is compatible with all versions of Microsoft Access – from 2007 to 2019.

Closure

The error “The object was saved in an invalid format and cannot be read” usually appears if the Access application fails to read the objects (forms, reports, queries, etc.) in the database file. You can decompile the database and then recompile it, uninstall the updates, and follow other troubleshooting methods described in this post to fix the issue. If the issue has occurred due to severely corrupted database file, then consider using Raminfotech Repair for Access. It can repair corrupted forms, queries, tables, and other objects in the database file. You can download the trial version of the tool to scan the corrupt .accdb/.mdb file and preview the repaired objects.

 

Post a Comment

0 Comments