Corrupted a file now get "no suitable backend found"

Dennis Shimer dshimer at gmail.com
Sun Nov 17 13:32:39 EST 2013


That was lesson #2 don't set the time higher than the amount of typing you
are willing to use.  I actually know both lessons and thankfully this was
test data but it really underscored the necessity of good data practices
because this will be important once I start for real.


On Sun, Nov 17, 2013 at 10:32 AM, Colin Law <clanlaw at googlemail.com> wrote:

> On 17 November 2013 14:12, Dennis Shimer <dshimer at gmail.com> wrote:
> > Right, obviously lesson learned.
>
> Just in case you did not realise, gnucash makes automatic backups each
> time the file is saved.  If you look in the same folder as the
> accounts file you will find files named as your account file with a
> timestamp and .gnucash on the end.  You should be able to open the
> most recent of those, which will just have the last lot of changes
> missing.  If you do that then don't forget to do a Save As and change
> it back to the correct name again.
>
> Colin
>


More information about the gnucash-user mailing list