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.