1

Ninox on iPad Stopped Saving Changes

It's only happened once, and I got around it, but it's made me nervous about making changes, so I'm hoping for a bit of feedback - has it happened to other people, and is there something different I should have done?

Working on a Ninox database on my iPad, and noticed a couple of things I thought I'd changed, but obviously hadn't. Fixed them and carried on. Came out of the database, returned to it, and the changes I'd just made hadn't saved. Multiple changes across several records, with different data types.

Made the changes again, closed and re-opened database, gone again. Tried again, same.

I then did a 'reorganize database', tried again, and the changes saved ok.

The problem is now, obviously, I'm worried it will happen again. And if I don't notice in time, I'll have wrong information in the database, and won't realise.

For background, the iPad owns the database, and always has. Synced with iCloud, also accessed, but rarely updated, from my iPhone.

I'm wondering if it's connected to sync, and maybe I should have opened and closed the database on the iPhone too, to let that save any updates. Or even if the iCloud sync can cause this sort of problem, should I stop using it entirely? I'd rather have a database I can rely on but only access from my iPad than one that might lose data that's accessible from both devices.

4 replies

null
    • michael.5
    • 4 yrs ago
    • Reported - view

    Sorry - that looked less like a wall of text in the editor, with its double paragraph spacing!

    • Alain.1
    • 4 yrs ago
    • Reported - view

    I also had a backup problem on icloud. After restoring my database, I had lost data (photos and pdf) related to data.
    I managed to recover the information by importing the data from an old backup. The problem is that I had all the data duplicated, I had to erase the ones that didn’t have the files related to the photos and pdf.. and recreate the one that was not saved. Since then I have made several backups, on Ipad, iCloud, hoping it doesn’t happen again.

    • UKenGB
    • 1 yr ago
    • Reported - view

    I also have seen this, recently, on the local Mac app sync'ing via iCloud. I spent a day adding data and then later on (after closing the db to save an archive and re-opening) noticed the recent data was simply missing.

    Creating a new db by importing an archive (the one being created above) and no more problem. However, if I revert back to the problematic db, it still will not save data.

    Looking at Ninox's files I can see that the data.db file (the real database) is not being updated, it silently does not save the new data when it is supposed to and when subsequently re-opening the db, that new data is not there.

    No obvious reason I can see why as the perms etc of the files are all correct, but that db will simply NOT save any data, only structural changes are saved. Yet a duplicated db works fine, as does the new one created from the archive, although neither of course contain the missing data. That's gone.

    Seems kinda worrying to me, to say the least.

    • Holly_M
    • 1 yr ago
    • Reported - view

    I've encountered this problem twice now as well, and I am extremely nervous and wondering if I need to take the Db to a local working copy. I can't be entering data for who knows how long only to find out at a later date they didn't get saved. I also did the Save As archive and I wonder if that is related but I've haven't tested since this is a massive problem as it impacts data integrity and has Ninox acknowledge this as an issue? Also is there any way you can "tell" if the iCloud DB is current so I can at least check to make sure exiting the Db, rebooting, etc won't cause a data lose?

Content aside

  • 1 Likes
  • 1 yr agoLast active
  • 4Replies
  • 1024Views
  • 4 Following