Hello,
I have various databases, and I usually use a particular set of preferences with each of them. For example, with different databases, I need a different layout of the columns that display in the List View.
I would like to know if I can use different Preference files (or alias to them) to start Bookends, without incurring problems.
Thanks,
Multiple preference files?
Re: Multiple preference files?
Hi,
No, one preference file. Each database has some settings that are unique to it (e.g. the database it syncs with), but things like the identity of the columns in the list view apply to all. This isn't going to change.
Jon
Sonny Software
No, one preference file. Each database has some settings that are unique to it (e.g. the database it syncs with), but things like the identity of the columns in the list view apply to all. This isn't going to change.
Jon
Sonny Software
Re: Multiple preference files?
julesmim,
An obvious solution—though far from elegant—would be to have a separate account in MacOS for each one of your libraries. The scope of Bookends preferences, as far as I can tell from a quick look in the Finder, is the user level, not the machine level.
To be able to access your work from all these accounts, obviating a separate copy for each account as well as a manual or automatic syncing scheme, you would need to change your folder privileges accordingly in the main user account, where all your work resides.
I personally don't think it's worth the hassle and overhead, but it's a solution if the need is overriding.
An obvious solution—though far from elegant—would be to have a separate account in MacOS for each one of your libraries. The scope of Bookends preferences, as far as I can tell from a quick look in the Finder, is the user level, not the machine level.
To be able to access your work from all these accounts, obviating a separate copy for each account as well as a manual or automatic syncing scheme, you would need to change your folder privileges accordingly in the main user account, where all your work resides.
I personally don't think it's worth the hassle and overhead, but it's a solution if the need is overriding.