Questions And Answers
| Q: |
Can Recovery for Access repair my Access database? |
| A: |
The effective way to find out if a Access database is recoverable is to try the demo version of Recovery for Access on it. Visit the Demo page for a free copy of the demo.
Product specifications with lists of items recovered and not recovered is available at the Product Information page.
Note: Always backup your original corrupted Access database before proceeding with any recovery activity! |
| Q: |
What limitations does the demo version of Recovery for Access have? |
| A: |
The demo version recovers a limited number of rows in each table of the corrupted database. The remaining rows will contain "demo" in text fields and null values in other types of fields. Forms are not restored, but replaced with blank demo-form. Full version of Recovery for Access will recover the demo-limited rows and forms as well.
No additional information, objects or features of the original database will be recovered by commercial version of Recovery for Access if not present in demo output. |
| Q: |
I have tried the demo. How do I decide whether to purchase the full version of Recovery for Access? |
| A: |
Evaluating the results of demo recovery can help in making the decision. |
| Q: |
What are the differences between product licenses? |
| A: |
Details of current licensing scheme are described at the Licensing page. |
| Q: |
Why do results of recovery contain less data than the original Access database? |
| A: |
This is normal. The damaged parts of your Access database will convert to zero size on output. The other common reason of file size decrease is when some of features of the original database are not supported and therefore absent from the recovered database.
Demo-recovered database is smaller because it mostly consists of demo placeholders than actual data. |
| Q: |
Running Recovery for Access from command line (through Windows Start -> Run menu). |
| A: |
If your license type is Enterprise or Service, you can run Recovery for Access from command line and use these calls in your batch files. Standard version does not support command line. The format for command line call is:
ar.exe <original filename with path> "<path to directory to store the recovered file(s)>"
(without angle brackets).
Please note that the directory for recovered file(s) should be created before starting the recovery.
Command line mode supports patterns '*' (replaces group of symbols) and '?' (replaces one symbol).
|
| Q: |
Recovery for Access does not work though Access 2.0 is installed on the computer. |
| A: |
Recovery for Access needs a 32-bit version of Access to be installed while Access 2.0 is an old 16-bit application.
Though Recovery for Access is able to recover Access 2.0 databases, it requires Access 95 or later version to be installed. Access 2.0 does not provide Recovery for Access all the functionality required to recover the corrupted database.
To resolve the problem install the 32-bit version of DAO library or process the normal installation of Access 95 or later version of this software. |
| Q: |
What will be the Access version of recovered file? |
| A: |
The version of resulting database depends on the version of Microsoft Office and DAO installed on the system where the recovery process is held. By default it is the lowest (oldest) version available starting from Access 2000. |
Recovery for Access Error Messages
| Q: |
Recovery for Access Error: Internal Program Error message. |
| A: |
Run Recovery for Access in a logged mode and contact our support team with detailed description of the problem and the log file.
To create log file, please hold the SHIFT key while clicking the Recover button on the toolbar of Recovery for Access or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching Recovery for Access. |
| Q: |
Recovery for Access Error: Not enough disk space. |
| A: |
To fix this problem you need to set temporary directory to the drive with free space available (2-3 times of the original database size). Fix the Windows environment variable to use it. Do the following:
- Open System in Control Panel.
- On the Advanced tab, click Environment Variables, then click the name of the user variable (TEMP or TMP) you want to change.
- Click Edit to change value.
- Set path to the location where temporary data should be stored (e.g., e:\).
- Restart computer for changes to take in effect.
- Run the software again.
You can also use the special environment variable called OFFICERECOVERY_TMP to set the directory where Recovery for Access should store its temporary files. Use the method shown above to add/edit environment variable. |
Access Error Messages
| Q: |
Cannot open database '*.mdb'. It may not be a database that your application recognizes, or the file may be corrupt |
| A: |
All versions of Access |
| Q: |
The database '*.mdb' needs to be repaired or isn't a database file.
You or another user may have unexpectedly quit Microsoft Office Access while a Microsoft Office Access database was open. Do you want Microsoft Office Access to attempt to repair the database? |
| A: |
All versions of Access |
| Q: |
You do not have the necessary permissions to use the '' object. Have your system administrator or the person who created the object establish the appropriate permissions for you |
| A: |
All versions of Access |
| Q: |
The database '*.mdb' can't be repaired or isn't a Microsoft Office Access database file |
| A: |
All versions of Access |
| Q: |
The Microsoft Jet database engine could not find the object 'MSysCompactError'. Make sure the object exists and that you spell its name and the path name correctly |
| A: |
All versions of Access |
| Q: |
Unrecognized database format '*.mdb' |
| A: |
All versions of Access |
|
|
|
