Monday, March 22, 2010

Repair a damaged Jet 4.0 database in Access 2000

Environmental factors also leave your database file damaged. The symptoms of a corrupted database can start by showing that certain of your records are deleted, to the inability to open one of the objects in the database, to the complete inaccessibility to open the access database file. The inbuilt Compact and Repair utility in MS Access is a useful tool that you can use to recover and to optimize MS Access 2000 database files. But if database corruption persists even after running the above utility, then you will need to use a commercial Access Database Recovery application to repair your database.

Important Guidelines for Running the Compact and Repair Utility

Before you can run the inbuilt “Compact and Repair” Utility on a database, take care of the following conditions:
  • You must logon with an account that has Modify Design or Administer security permissions for all tables in the database.
  • Enough disk space must be there for both the original and the compacted versions of the database.
The repaired or compacted database is renamed as the original database only when the Compact and Repair utility is successful.
Other users must not have the database open.

When a database is compacted, the database must be opened exclusively by Microsoft Jet to prevent any users from accessing and from modifying the database during the process.

Run the Compact and Repair utility as follows:
  1. If the database is open, close it.
  2. On the Tools menu, point to Database Utilities, and then click Compact and Repair Database.
  3. In the Compact Database From dialog box, click the file that you want to compact, and then click Compact.
  4. In the Compact Database Into dialog box, enter a new file name, and then click Save.
If the compact and repair does not succeed, you receive a message stating so. This means the damage is so severe that the damage cannot be corrected by compact and repair utility, then you will need to opt for a third party Access Database Repair software. These Access Recovery tools scan the corrupted database objects, repair them and restore the repaired object at user specified location.

Friday, March 19, 2010

MDB file corruption due to Interrupted Write Operations

A normal MS Access database user opens and closes its database file (MDB) various times in a single day. Alterations, such as, updation, addition, and deletion in database files are performed to fulfill all the personal or professional requirements. Since, the database is opened and closed numerous times, the probability of improper shutdown always persists. In most cases of unexpected shutdown (manually turning of the system), the Jet database write operation is interrupted. The Jet database engine sets a flag while beginning a write operation, and resets the flag when the operation is complete. However, if the database engine write operation is interrupted, the flag remains set and when you attempt to start your database, Jet reports that your database has been corrupted. To overcome such corruption situations, a valid database backup enables you to restore the data. However, if no backup is available or backup falls short to restore the required data, then you will need to use advanced access recovery application.

As a practical case, you accidentally perform improper system shutdown of your system when some write operation was being executed. However, when you restart your system and attempt to mount your database, you receive an error message stating that your database has been corrupted. Furthermore, the records stored in your database become inaccessible. To access the records after database corruption, you will need to repair the database using the underneath steps:

· Select “Database Utilities” on the Tools menu
· Click on Compact and Repair Database.
· Search for the database file in the ‘Database to Compact From’ dialog box
· Click on Compact.
· Choose a new folder destination for the new file in the ‘Compact Database Into’ dialog box.
· Provide a unique, valid, and new name for the database file
· Click on Save.

If the repair utility is unable to repair your corrupted database, then you will need to opt for third-party access database repair application. Such Access Repair applications employ powerful scanning methods to recover lost Access database recovery components and repair corrupt MS Access database.

Access Recovery is a user-friendly tool that provides preview of all recoverable database objects through its demo version. The non destructive Access Repair tool is compatible with Microsoft Access 2007, 2003, XP (2002), and 2000 and restores the recovered data on the new or user-specified location.

Thursday, March 11, 2010

Resolving errors post Microsoft Access Jet database Engine corruption

The core database engine for Microsoft Access database is Microsoft JET Database Engine. The database engine handles your MS Access database by using three different modules. The JET (Joint Engine Technology) add various functionalities to MS Access, such as, enforcing referential and entity integrity, transaction processing, simultaneous multiple-database users access, and more. While the Microsoft JET Database Engine provides incomparable benefits, a small corruption in the database engine can result in serious damage of Access database files. In such situations, the ideal way is to restore the Access database files from an updated backup. However, if no backup is available, then you need to use advanced access database repair tool to repair your database files.

The error message that you might meet after your Access database gets corrupted due to Microsoft JET Database Engine damage:

“The Microsoft Jet database engine could not find the object 'filename'. Make sure the object exists and that you spell its name and the path name correctly”
Or
“Microsoft jet database engine could not find object MSysDB. Make sure the object exists and that you spell its name correctly and the path name correctly”
Or
"The Microsoft Jet database engine could not find the object 'databases'. Make sure the object exists and that you spell its name and path name correctly"
Or
“Microsoft Jet Engine can't open the file”

Due to these error messages you are not able to access the records from your database when you try to mount your database.

Microsoft JET Database Engine damage or corrupt due to improper system shutdown, application malfunction, human errors, and virus attacks.

To resolve all above error message and access the records from database files, you need to opt for advanced access repair tool. Such repair tools ensure safe repair of database without modifying the original content of the database.

Sunday, February 14, 2010

"Unexpected Error 35012" When You Open a Database.

We always store office work in form of database. For maintaining and creating database, MS access is best software utility. As it is easy to use but sometimes when we try to open an existing MS Access Database, you may get an error message:

“Unexpected error 35012”

Due to this error your database closes unexpectedly. You face this error due to the corruption in the Microsoft Access Database or mdb file. These corrupted objects may include one or more database forms of reports.

As Microsoft has provided compact and repair utility to repair access database and several other utility is form of patch to resolve this problem such as jet compact utility. One more method is there to repair the corrupt database i.e import the corrupted .mdb file or object in a new file. For importing corrupted database, follow following steps:

* Create a new Access database
* In file menu, select Get External Data option
* Select Import from Get External Data
* Select all the database objects in the file and import in newly created database

If you again face "Unexpected error 35012" when you import a specific object, try the 2nd step again. If you fail to import this time also, you will need to restore the corrupt object from backup.

But it helps only when your database is less corrupted. If it is critically corrupted then compact and repair utility or jet compact utility doesn’t help you. Even you can’t import database. In case if you fail to import the database and you don’t have any backup, then you can’t repair your database without using 3rd party access repair tools. In these situations, your entire database may become inaccessible. Access recovery softwares are the powerful data recovery programs that can search and locate your corrupted access database and can repair them.

Friday, January 29, 2010

Error Message after exporting an MS Access Table

Exporting MS Access database components in MS Word Merge format or MS Excel format is the common practice followed by database users. While exporting the database objects provides various benefits, it can also become a cause of Access database corruption. In many cases, the Access database becomes inaccessible and demountable. To regain the affected database data, you should restore the Access database from an updated backup. However, if you have not created any such backup or the backup fails to restore data, then you need to use advanced access database recovery tools.

Consider a practical example, where you receive the below error message when you export a table (Employee) from a Microsoft Access database (in .mdb format) to the Microsoft Word Merge format:

“The data being exported does not match the format described in the Schema.ini file.”

Furthermore, you receive another error message if you use VBA (Visual Basic for Application) code:

Run-time error ‘3438’

Cause:

The main cause behind the above error message is that when you export the Employee table for the first time, the field names of the table for the Microsoft Word Merge format get saved in the Schema.ini file. A schema.ini (schema information) file provides information about the general format of the file, column name and data types. So, if you again export the employee table, it does not match with previously exported fields. Another major reason behind mismatching fields can be Access database corruption. In both the cases, if you try to import the Employee table, you will receive the above error messages.

Resolution:

To resolve the errors, Microsoft suggests opening the schema.ini file by using Notepad and then modifying all the field names that are causing the problem. However, in case of database corruption, you need to repair the MS Access database and then apply the above resolution. To completely repair the MS Access database, you should use advanced access repair utilities. Such Access Recovery tools incorporate effective scanning algorithms to perform thorough repair and restoration of all affected Access database components. These applications can be easily understood without prior technical knowledge as they come with largely graphical interface and user-friendly documentation.

Tuesday, January 26, 2010

Error Message after exporting an MS Access Table

Exporting MS Access database components in MS Word Merge format or MS Excel format is the common practice followed by database users. While exporting the database objects provides various benefits, it can also become a cause of Access database corruption. In many cases, the Access database becomes inaccessible and demountable. To regain the affected database data, you should restore the Access database from an updated backup. However, if you have not created any such backup or the backup fails to restore data, then you need to use advanced access recovery tools.

Consider a practical example, where you receive the below error message when you export a table (Employee) from a Microsoft Access database (in .mdb format) to the Microsoft Word Merge format:

“The data being exported does not match the format described in the Schema.ini file.”

Furthermore, you receive another error message if you use VBA (Visual Basic for Application) code:

Run-time error ‘3438’

Cause:

The main cause behind the above error message is that when you export the Employee table for the first time, the field names of the table for the Microsoft Word Merge format get saved in the Schema.ini file. A schema.ini (schema information) file provides information about the general format of the file, column name and data types. So, if you again export the employee table, it does not match with previously exported fields. Another major reason behind mismatching fields can be Access database corruption. In both the cases, if you try to import the Employee table, you will receive the above error messages.

Resolution:

To resolve the errors, Microsoft suggests opening the schema.ini file by using Notepad and then modifying all the field names that are causing the problem. However, in case of database corruption, you need to repair the MS Access database and then apply the above resolution. To completely repair the MS Access database, you should use advanced access database repair utilities. Such Access Repair tools incorporate effective scanning algorithms to perform thorough repair and restoration of all affected Access database components. These applications can be easily understood without prior technical knowledge as they come with largely graphical interface and user-friendly documentation.

Monday, January 18, 2010

Resolving “Disk Space” error messages in MS Access

A page in MS Access database is the smallest amount of storage area. Modifications or alterations performed in Access database should be performed by temporarily locking all the pages it contains. This prevents database corruption as two or users may not be able to modify the database simultaneously. However, if the prevention is not taken and the pages remain unlocked, the probability for database corruption remains. The best way to overcome any type of corruption in the Access database is to restore the data from an updated backup. However, if no backup is available or backup fails to restore the required data, then you will need to use advanced Access Recovery applications that can completely repair the corrupted database.

As a practical case, you encounter any of the below error messages when you attempt to mount your Access database (Accounts):

"There isn't enough disk space or memory."
Or
"There isn't enough disk space or memory to undo the data changes this action query is about to make."

You encounter the same error message each time you attempt to mount the database. Data stored in the Accounts database becomes inaccessible after any of the above error messages appear.

Cause:

The root cause for the occurrence of the above error message is the exceeding of the 9,500 locks per database file limit. The above error messages primarily occur while mounting large databases. To prevent the occurrence of any of the above error messages, you will need to increase the default decimal value of 9500 in the Value Data field.

Resolution:

To resolve the above error message and access the database, you will need to need to make some changes in the Windows Registry. A slightest of mistake while making changes in the Registry can result in serious problems. To overcome all those problems and access the database, you will need to use advanced Access Repair applications. Such Access Database Recovery utilities employ advanced scanning algorithms to comprehensively recover all Access database components. These applications can completely recover and restore inaccessible Access databases. Built with highly interactive and graphical user interface, these repair utilities are easy to understand without the need of any prior technical understanding.

Access Recovery is a feature rich Access Database Repair application. This repair application can restore and Repair Access database components including queries, forms, reports, macros and modules. The read only software supports Microsoft Access 2007, 2003, XP (2002) and 2000. It is designed for Windows Vista, XP, 2003, 2000 and NT.