1

Views are not saved when I close database

Using Ninox locally on my iMac.   I create new views (usually Table views) or modify existing views - both in normal and editor mode.  When I close my database and come back in - the views may or may not still be there.  In other words - Ninox is not saving my changes to the views (adding new views, adding/removing fields to the views, etc.).

Is there something special I need to do in order to get Ninox to retain my view changes?

10 replies

null
    • Fred
    • 3 yrs ago
    • Reported - view

    Make sure you are in Admin mode (red wrench is active) before you make any changes. 

    • K_Gamble
    • 3 yrs ago
    • Reported - view

    Yeah - I do in Admin mode - but sometimes the changes stay and sometimes do not.  I'm not sure what the 'thing' is that prompts the save.  Still occurring - cannot determine why.

    • Krohn
    • Ninox_Krohn
    • 3 yrs ago
    • Reported - view

    I have the same problem

    • K_Gamble
    • 2 yrs ago
    • Reported - view

    Anyone ever found a solution for this?  I cannot determine what makes the view changes stick and what does not.  I close my database, and when I reopen - some changes may be there and some not.  Whole 'new' views are gone, or changes within a view are no longer.  Then sometimes they are.  I've tried making the changes in Admin mode, or making other 'admin' changes after I create the view.  But I cannot determine why it will work sometimes.  Frustrating as I have had to recreate views over and over before they magically stick around.

    • Fred
    • 2 yrs ago
    • Reported - view

    Just make sure you are in admin mode before making changes. I have not had any issues with changes not being saved while in Admin mode.

    I think it is a bad UI design that lets you do something but not save the results. I get caught up in making changes and forget admin mode and then lose my changes.

      • K_Gamble
      • 2 yrs ago
      • Reported - view

      Fred I wish that was the answer.  I've tried many times in Admin mode.  Doesn't help.  I'm on a mac and doing everything locally (not cloud) - not sure if that is where the problem is isolated to or not.

    • Fred
    • 2 yrs ago
    • Reported - view

    I to use the Mac app. I'm running v3.5.14.

    I went back to test and on DBs saved to either iCloud or local I was:

    1) able to create a view in NON admin mode and it was saved when I exited the DB and re-entered

    2) able to create a view in admin mode and it was saved when I exited the DB and re-entered

    • derrick_ashby
    • 2 yrs ago
    • Reported - view

    I have this problem also. I use the standalone app on the Mac as well.

    • Gianluca
    • 2 yrs ago
    • Reported - view

    I have sometimes the same problem too. Even just the name of the view sometimes doesn't get saved. And more: sometimes formula fields don't show immediately the result, but they will after I exit the view and re-open it. I am on Mac App too and saving locally.

    • UKenGB
    • 1 yr ago
    • Reported - view

    I had it just the other day. All views I had painstakingly created that day were gone when re-opening the db. I am almost always in admin mode as I'm constantly changing stuff as I use the db, so not that.

    I have to say, it's only happened the one time (that I've noticed), but also recently had a problem where Ninox simply would (silently) not save any data entered prior to closing the db. An imported archive of that (faulty) db did NOT have the problem and it continues to save now as it should, but that version of the db which had the problem, still does if I look at it again. Fortunately I don't need to but keep it anyway in case I need to show the problem.

    Not wanting to hijack this thread, but it is significant that Ninox can sometimes cause such serious problems, while being very hard to create them 'on demand' to illustrate to others.

Login to reply

Content aside

  • 1 Likes
  • 1 yr agoLast active
  • 10Replies
  • 485Views
  • 5 Following