[Zubersoft]

That approach is very similar in nature to just letting the user pick a database file to use as the active library. Unfortunately, there is a little bit of a snag if I try to provide different application settings per database. Google completely abstracted access to these files, so that you aren't really supposed to know where they are kept. You just go through their SharedPreferences classes and get/set values. That means that I can't easily change where these settings files are stored. This is true regardless of the approach I use for providing separate databases. If I wanted to keep separate settings for each database, one approach would be to copy all of the settings files into a directory that has to live at the same level as the database file, so that when you switch to that database file, I overwrite the current application settings with those ones. This doesn't work well if one of your databases is the one in the default location though, as those settings would be overwritten, so I would also have to automatically back up those settings when you switch away from the default location. Ultimately, I don't think all of that really matters though, as why would you want different settings per database? Wouldn't you want the same settings applied to all of your databases?

The simplest thing in my mind is to provide an option to select a different database file, and if some of the settings are important, these can be saved alongside the database file. I think each of these database files should be uniquely named so maybe I would have to think about how to handle that. As new databases are set up, the user can easily switch between existing databases in a list. If "Manage my Files" is off, users can pick where they want the database to be stored for each library. If it's on, the user can only provide names for each library, but they will all be created in the default storage location.

Thoughts?