[sciurius]

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.

So this is as far as we can get, then.

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?

I think it's a restriction I can live with...

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.

Maybe an identifier to use as postfix, e.g. "mobilesheetspro_MyProject1.db" "mobilesheetspro_AnotherProject.db" and similar? The pick list would then only show "MyProject1", "AnotherProject" and "<default>".