Database Degradation
Was wondering if anyone else has experienced issues with their database where scripts stop executing, formulas calculate haphazardly and dynamic choice fields only work sometimes. This all has happened to me in the last couple of weeks, and there has been no development or work on the database (other than data entry) in that time. Even simple things like
-a formula field in a table displays the correct value when in the record view, but in the table view, it doesn’t display the same number.
- a Trigger on create script doesn’t alway fill in the field.
This is with a cloud subscription. Opening it on a web browser. I have contacted Ninox for help, but they have not been able to provide any explanation as to why this occurs, just suggestions for work arounds. I am unsure if this has happened because I have added functions to the database over time. Still doesn’t explain (to me) the reason it worked for a bit and then stopped.
So that main reason I am asking is that I am contemplating re-writing the database and transferring all my current data in hopes that I don’t get the same problems. It really has put doubts in my mind to the long term stability of Ninox and the flexibility it allows for future feature expansion.
4 replies
-
Brendon
I can't give you an answer - but I have been using the cloud version to run my business on for the last 2 years. With multiple users/ multiple tables, many triggers and formulas for batch updating/copying data from one table to another etc. The main table now has over 660,000 records in it and all I can say is that from slight bugs apart - (name software that doesn't have these!) it is functioning as expected and I get nothing like you describe all fields/forms etc display correct in all forms ie on the form/table view etc.
Also as I access Ninox in several places I can confirm it operates normally on both fibre and ordinary broadband (albeit it slower!)
In case you have not tried this! and I know it might sound daft. But as you are on the cloud version you get the benefit of backup and restore (restore always copies back to a new file so you don't lose your current DB. So it might be worth trying and then running tests in the backupfile to see if you get the same results.
Before you recourse to start again on a new version of your database
It might be worth trying a completely new database using one of ninox's preset templates. Then add a few formulas
and simply flood filling it with random data from csv import.
Only other things I do are :-
I turn off every field setting for global search where I don't need it.
I don't index any files (tested this many times and it don't seem to make any difference) so I don't have it set
I take a manual backup once a week (just in case the auto backups fail)
I do everything twice (in terms of development) ie I try out mods in the play copy first!
Hope you get it solved soon.
Mel
records in one of my tables
-
Hi Mel,
Thanks for taking the time to respond. And I appreciate all the encouragement.It’s good to know (in some way) that this is probably my fault, and not just an unlucky glitch. (Yes, I do understand that nothing is perfect)I do have a bunch of manual backups. Usually one a week that I download and store locally. The only reason I was looking at starting again is that I am concerned that I have some poorly written code (that is no longer being used) that I am carrying over and now is causing an issue with new features that I have rolled out. This is my first proper foray into a database.
Cheers,
Brendon
-
Good news, I managed to figure some of it out. The trigger on create was being blocked by a trigger after update script on the date field. Not that any of those have anything to do with eachother, but as soon as I deleted the line, the trigger on create worked again.
-
Brilliant
Glad you got there :-)
Content aside
- 3 yrs agoLast active
- 4Replies
- 409Views