Zugriff auf myDB in mehreren Screens

[DietrichV]

Ich habe in Screen1 eine TinyDB mit Namen myDB definiert und mit Daten gefüllt.
Im zweiten Screen wollte ich diverse Aktionen mit myDB durchführen.
Allerdings wird myDB nicht gefunden, obwohl ich den gleichen Namen verwende.
Was mache ich falsch?

[kunj_thakker]

this may help you

Bad arguments to select list item

In both cases, it depends on the Namespace value of the TinyDBs, which determines the XML file name used for Tinydb components. If you have not changed the default Namespace value (“TinyDB1”), you should find the same TinyDB1 in all screens of an app. Your initialization error in a real device is probably caused by using an inappropriate notfound value in your initialization loads from TinyDB1, like a blank text block where an empty list is warranted. See How to Deal with notfound from looku…

[DietrichV]

Genügt es, das “set Namespace” einmal beim Initialisieren des Screens auszuführen oder muss es immer vor jedem Zugriff auf die TinyDB ausgeführt werden?

[ABG]

It has been a matter of debate whether to keep switching the Namespace attribute of a single TinyDB component to access different data stores, versus just pulling in more TinyDB components in the Designer and permanently renaming them by purpose and setting their namespaces appropriately in the Designer.
(I recently posted a sample of this in the samples section at Fruit Stand: TinyDb Namespace sample)
where you can use the translate option for hopefully easier reading.

The tradeoff is between run time memory usage (how many XML files are open at the same time) versus code complexity (reusing a component for different purposes imposes a burden on the programmer to remember what purpose is currently being served by that component. (I dislike such burdens.)

[DietrichV]

Where are in your example “Fruit Stand” the
“set TinyDB_Prices namespace prices” and
“set TinyDB_Purchases namespace Purchases”?