How do I run SecureRecovery fo Works Database from the command line?
To run our software applications through a command line (the Start -> Run menu in Windows), you will need to own an Enterprise or Service license. The command call is as follows:
Avoid the use of angle brackets, and use the patterns below to replace symbols/characters.
‘*’ - Replaces groups of symbols. Usage: *.wdb
‘?’ - Replaces one symbol. Usage: ???.wdb
Create a folder/directory for the recovered database files before executing the program.
I am interested in this software, but I am not sure whether it can repair my Works database. Can I try it before I buy it?
Yes. We offer a free demo of SecureRecovery fo Works Database, which allows you to recover several rows from the affected database. It uses placeholders for all of the other recoverable rows, so you can accurately determine whether the program will work as expected.
The full versions of SecureRecovery fo Works Database do not have any limitation on the number of recoverable rows or databases.
A row, table, or other element is missing from the demo output. There are no placeholders to show that it is recoverable. What does this mean?
Unfortunately, severe corruption can prevent the recovery of some elements in extreme cases. The full version of the software will not be able to recover anything that is not present in the demo.
Why do I need to back up my database before running SecureRecovery fo Works Database?
Backing up your original Works databases will allow you to make additional recovery attempts if there is an issue with the first attempt. You should always back up your files before taking any action to repair corruption or file damage.
How can I get help when choosing a product license option?
Review our full license scheme (available on the Licensing page) to make an appropriate decision.
After I complete my recovery, I can access my database and it seems to work properly. However, the file size is different from the original copy of the file. Is this a bad sign?
No, this is a normal result of the way that SecureRecovery fo Works Database processes damaged information. Corrupt files often contain unreadable sections, which are left out of the recovered database. This reduces the file size. Additionally, you may notice that databases recovered by the demo version of the application are significantly smaller due to the presence of placeholder text in the recoverable rows.