If you haven’t downloaded Oops! File Manager yet, I’ll say give it a try. This article is mostly about the OFM database. If you haven’t read any relatable articles on OFM then let me reiterate by saying that OFM uses a single file database to store everything that’s going on with the application. This makes the possibilities of this file to be corrupted or overwritten, a little high but still rare.
However, the most confirmed way of damaging the OFM DB is installing updates. When updating OFM you must only use the “Update_Only” install file to make sure that the installer doesn’t overwrite the DB by accident. If you are downloading it for the fist time then the regular install file will work fine. If by some freak of nature you use the typical “setup” install file, while trying to update your older version of OFM, then its a good chance that the OFM DB is gone.
To stop this from being a possibility, locate the DB file (
OFMdb.sdf) in the installation folder, which should be in the “AppData\Roaming” folder (i.e.
C:\users\yourUserName\AppData\Roaming\Oops File Manager\). After you found it, simply copy it to a safe place. If this ever becomes a reality you can easily restore it by moving it back to the install folder.
SNEAK PEEK: Good news is that version 1.2 of Oops! File Manager will have a built in database backup that will happen every 5 days. Right now it is locked in at every 5 days; however, we are exploring the options of the Professional Edition having the ability to change it.
As always, thanks for reading!