MAJOR problem (v3.7.14 Mac)
Made some changes yesterday for first time in a few months. Made some minor structural modifications and went through a fair bit of data, updating to suit the changes (a new field or 2). All was proceeding according to plan.
This morning (not shut down in between) I wanted to remove an old field and since Ninox provides NO means to search for occurrences of a field, I duplicated the database first (structure AND data), before deleting the field, just in case. In fact I had only missed one instance and was easily able to fix that.
A while later I noticed some old data that I KNOW I changed this morning. On further checking, ALL data changed since I started yesterday has reverted back. So NOTHING I have done to the data has been saved. The modifications to the structure are intact, but changes to data have been discarded. E.g. a new (lookup) table I added is there, but NO records, zero, zilch. The entire table has been 'reset' and all records entered this morning are gone.
I checked the copy I had made and that is also missing all the data changes since yesterday, so presumably all that new data was discarded before making the copy.
Ninox updated itself a few days ago, but I only started making changes since then.
I'm not partial to wasting hours (or more) to have it all thrown away. Either this is a HUGE problem, with Ninox failing to save data (its PRIME function of course) or somehow I have missed something that tells Ninox to not save changes to data, which would be news to me if it existed.
What can I possibly have done to cause this, or has Ninox completely let me down and trashed my data?
Before typing the above, I entered new records into the table that had been 'emptied', so it was as it should be (and had been). In the time it took me to type the above, the same table has again been emptied.
In fact, I am unable to save ANYTHING.
Every time I close the database, like going to 'My databases' at the top of the left panel, it throws away any data changes since it was last opened - although as I said, structural alterations ARE saved.
No reason I can see why it is not saving data. If it cannot write to the file, surely it should display an error to state that. As it is, it's just silently throwing away all data changes.
Only change I can think of since it was working (months ago) is that I am running from a different drive. For reasons not worth getting into here, I copied everything to a new drive and am now using that as boot and main drive. All working as it should, except 'Watch unlock' that did work, but now refuses. No idea why, but I doubt has any connection to Ninox's current aberrant behaviour.
I updated my MacOS app to 3.7.14 last night and I can't duplicate your issue. I've added new records and modified records and even when I quit the app and then go back in all the changes are there. I did this on a local stored DB and one stored in iCloud.
For the new records not showing up, I would say check to make sure you have not filtered your view in a way that would not show the new records. I've done this before and freaked out that things are broken.
For modified data, I don't know what to say.
Looking in the folder where it is all stored and schema.json is updated whenever I make a structural change. But data.db (which I assume is the actual data file) has not been updated since Dec 12th, which is probably the last time I changed something and that was saved.
Ownership and permissions are exactly the same for these 2 files. So back to the same question, why is Ninox unable to save any actual data?
To be clear, it's not just that new table (which happens to conveniently illustrate the problem). Any change to other tables' data is similarly never saved. The data that already exists remains, but no changes or additions are saved. To any table that I have tried.
UKenGB As Fred said, I can't reproduce the problem either.
MacOS app v 3.7.14
Tried a different database (totally different, nothing to do with the first one) and just opening it caused its data.db file mod time to be updated, whereas NOTHING I can do to the other one updates the data file.
So something up with this database. A bit worrying that Ninox might do this, unprovoked. Now I need to figure if it's fixable.
Having previously created an archive, I imported that back in and that seems to be able to save its data.
I also tried the duplicate I made which although also doesn't have the missing data (thrown away when quitting the original db), it IS able to save data. I will use that.
So the main db that I was using is utterly stuffed and silently threw away almost 2 days work entering new data.
So I finally have a working db again, but I now have to re-create all that data and to say I am not happy would be a HUGE understatement.
I would email support.
Good morning and Happy New Year. I kind of have the same problem. I have a specific date field, which I tried to empty for one record, and after a went back to db screen and then again into the table, the date field wasn't empty but instead said "01/01/1970"!!!!!!!!!!!!!!!!! This is very troubling!!!!
For what it is worth
I am am on latest version (cloud) and in fact on the cloud one does not get a choice as soon as updated version is released you are auto updated (like it or not)
However over last few days I have been very busy doing 2023 mods - adding/deleting fields re thinking client cards and adding branch sub records and moving 1000's of records data. adding @seans dark mode etc
I honestly have not had a single issue with this version. so from a web point of view I would say it is a stable as I could expect.
UKenGB When you first updated to v3.7.14 and opened your main DB did you noticed that you didn't have the wrench in the upper right corner and have to "reorganize" the DB so you had admin rights to it? I finally opened my main DB, I track a sport so it is in the off season so I haven't had the need to enter in data yet, and noticed that I didn't have the ability to go into admin mode. When I reorganized the DB I had admin access again.
IT'S HAPPENED AGAIN!!!!
Yes, caps intended because this is really ******* me off.
Data I added late yesterday is gone and checking the files I can see that Ninox did not update the data.db file since 17h00 yesterday, after which the new data was added. The 'sync' folder has been updated, but that's not being sync'd to the actual data file and so when the db is re-opened, that last added data is gone.
So it was not a one-off.
This time it's even worse as even a reloaded archive will NOT save data.
Really, what is the point of a database that chooses to NOT SAVE DATA.
- 11 mths agoLast active