First, you need to ask yourself: why do you need 2 TinyDBs?
You could use firebaseDB or cloudDB instead since you don't have to pass the values between the screens.
If you're adamant. however:
(Note that I will only be using different namespaces instead of two components since it saves memory):
Make sure to change the namespaces and tags to your defined ones. You can duplicate the code if more than 2 tags per namespace; however, you could use a for loop to diminish the amount of recurring code in your app.
This behaviour have analogy with mysql> USE DepartmentDB/AccountDB and do some operations to the selected db. Having different namespaces in on Tinydb is similar to maintaining/managing different databases.
But having different TinyDBs under one namespace will be referring to the same storage space only, just as aliases.
Thanks TIMAI2, after having more clarity about Tinydb, I have a concern, there need to be a way to show/delete namespaces, which are there in a specific TinyDB, or it's not much useful/greaful to listing all associated namespaces with one TinyDB.
Perversely, you could save your namespaces in a list, then store that list in a tinydb for recall
Working with multiple namespaces in one tinydb also allows for the creation of distinct datastores at runtime. To be honest, it is up to the developer if they want to drag out additional components (tinydb) when creating their app, it may help to simplify development. The app user will, of course, be none the wiser as to how the app is constructed....