I was using the Local DB for the first time today for a simple “enter and then graph” data app (two fields), and I quickly discovered that (at this point in time) it isn’t possible to add rows to the Local DB.
I thought a simple work around would be adding “dummy rows” and then manually keeping track of where the real last row is by way of a stored local variable. I did put values (non blank) within the dummy rows.
While this strategy worked fine during any individual usage of the app (e.g. I can add a few rows, view a graph and see the new rows, add a few more, see the additional rows on the graph, etc.) the changes to the Local DB made using the SetCell method do not appear to be persistent beyond a single app session. Specifically, if I get out of the app and restart it, the Local DB changes I’ve made using SetCell are lost.
The Local DB.SetCell method also never appear within the “Click here to edit spreadsheet” design view, including while I’m using the app. I do however know the Local DB data is being changed by the SetCell method, as I pull data from the Local DB as a separate operation in order to graph it.
Is there some sort of Local DB property I may have missed that would enable persistence?
I should add here that I’m using an iOS phone platform, and that I know from practice that stored local variables are persistent across app usage (for example, the aforementioned actual last row of data variable).
Thanks in advance for any help you may be able to offer!