OfficeRecovery.com Home | News |

Recovery for FileMaker

Frequently Asked Questions

Table Of Contents

Questions And Answers

Can Recovery for FileMaker repair my FileMaker database?

What limitations does the demo version of Recovery for FileMaker have?

I have tried the demo. How do I decide whether to purchase the full version of Recovery for FileMaker?

What are the differences between product licenses?

Why do results of recovery contain less data than the original FileMaker database?

Running Recovery for FileMaker from command line (through Windows Start -> Run menu).

After successful recovery of the original database a new .DBF file is created. What is the procedure for transferring data from this temporary file to a database?

Recovery for FileMaker Error Messages

Recovery for FileMaker Error: Internal Program Error message.

Recovery for FileMaker Error: Not enough disk space.

Questions And Answers

 
Q: Can Recovery for FileMaker repair my FileMaker database?
A:

The effective way to find out if a FileMaker database is recoverable is to try the demo version of Recovery for FileMaker 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 FileMaker database before proceeding with any recovery activity!

 
Q: What limitations does the demo version of Recovery for FileMaker have?
A: Demo version recovers limited number of the database rows. The remaining rows will be blank. Full version will restore demo-limited rows as well.

Please, note that no additional records or tables will be recovered by commercial version of Recovery for FileMaker 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 FileMaker?
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 FileMaker database?
A: This is normal. The damaged parts of your FileMaker 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 FileMaker from command line (through Windows Start -> Run menu).
A:

If your license type is Enterprise or Franchise, you can run Recovery for FileMaker 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:

fmr.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: After successful recovery of the original database a new .DBF file is created. What is the procedure for transferring data from this temporary file to a database?
A:

You should simply import data from the resulting file in .DBF format into a new database.

Recovery for FileMaker Error Messages

 
Q: Recovery for FileMaker Error: Internal Program Error message.
A:

Run Recovery for FileMaker 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 FileMaker or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching Recovery for FileMaker.

 
Q: Recovery for FileMaker 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:

  1. Open System in Control Panel.
  2. On the Advanced tab, click Environment Variables, then click the name of the user variable (TEMP or TMP) you want to change.
  3. Click Edit to change value.
  4. Set path to the location where temporary data should be stored (e.g., e:\).
  5. Restart computer for changes to take in effect.
  6. Run the software again.

You can also use the special environment variable called OFFICERECOVERY_TMP to set the directory where Recovery for FileMaker should store its temporary files. Use the method shown above to add/edit environment variable.

 

Product Guide

Recovery for FileMaker

Product Home
Product Information

Demo

Free demo version is available.
Download

Order

Place an order
Sales assistance:
1-800-920-7713
Licensing

Support

Request support
Frequently asked questions

Company

Profile
Products
Customers
 

No portion of this website may be reproduced without express written permission by Recoveronix
Copyright © 1998-2008 Recoveronix Ltd.