Things to keep in mind about Recover:
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
i had the same problem without any recovery - a file on the server took forever to open - even filesize was onlu 300k. just 24 records
nothing fency - after our host restarted the server - well there might be some recovery i don't know happened - the file just increased its size
to 7 MB and i only use it as a counter for access. also committing a record took minutes and after some uptime hours - so i went back to a backup copy
before the server restart and unfortunately after a week of no problems with that tiny file all starts allover again. and now i recovered it and am praying
that i dont have the same issues with our main data file. - the server is windows fms11v3 the clients are mac and pcs 11v4 /v3 (pc).
If your have accidentally deleted your filemaker database, there is no need to worry as you can restore your deleted filemaker database with the help of Mac data recovery tool. It not only repair the damage database but also saves them in a location as per users choice. It also restores the lost files from other removable device that is USB, memory card etc.
For more information: