Wendy,
I'm really sorry to hear that you encountered those issues! Are you using the original MobileSheets (green icon) or the newer MobileSheetsPro (blue icon)? I just want to be sure I'm aware of the version you are using when offering advice. From the sounds of it, the database either had a critical problem of some kind, or was locked. When you restarted the app, the database still couldn't be started (the last instance of the program may not have been terminated by the OS yet), so MobileSheets probably tried to recover data by restoring an automatic database backup (just a guess). At that point, I would have suggested rebooting the device if you got into that kind of an error state... but both versions have an option in the settings to restore an automatic database backup. These backups are created daily, do you should have been able to restore the last known good database, which would have fixed everything. In fact, you still should be able to restore an automatic database backup from within the last week (which may be newer than the backup). Please look for this option, and let me know if you see a database backup that is fairly recent with a size that makes sense (it should be as large as or larger than the current database, which should be reflected in the last created automatic database backup in the list).
Something like this shouldn't happen in normal use, but database corruption is always possible I'm afraid. MobileSheetsPro does a better job of preventing this, as I now ship a known, stable version of SQLite with the app (this is the library that creates and interacts with the actual database file). If you did experience this problem in the newer MobileSheetsPro, then that is very concerning, as I've gone to great lengths to try to prevent data loss.
Thanks,
Mike
I'm really sorry to hear that you encountered those issues! Are you using the original MobileSheets (green icon) or the newer MobileSheetsPro (blue icon)? I just want to be sure I'm aware of the version you are using when offering advice. From the sounds of it, the database either had a critical problem of some kind, or was locked. When you restarted the app, the database still couldn't be started (the last instance of the program may not have been terminated by the OS yet), so MobileSheets probably tried to recover data by restoring an automatic database backup (just a guess). At that point, I would have suggested rebooting the device if you got into that kind of an error state... but both versions have an option in the settings to restore an automatic database backup. These backups are created daily, do you should have been able to restore the last known good database, which would have fixed everything. In fact, you still should be able to restore an automatic database backup from within the last week (which may be newer than the backup). Please look for this option, and let me know if you see a database backup that is fairly recent with a size that makes sense (it should be as large as or larger than the current database, which should be reflected in the last created automatic database backup in the list).
Something like this shouldn't happen in normal use, but database corruption is always possible I'm afraid. MobileSheetsPro does a better job of preventing this, as I now ship a known, stable version of SQLite with the app (this is the library that creates and interacts with the actual database file). If you did experience this problem in the newer MobileSheetsPro, then that is very concerning, as I've gone to great lengths to try to prevent data loss.
Thanks,
Mike