Brian, I had this same concern with Legacy 8 customization. The (ff) settings do make sense for multiple databases. The problem is that Legacy assumes that "Reset to Legacy-Defaults" should be used when opening a database for the first time in Legacy 8 versus "Reset to User-Defaults". Once the database has been opened, the (ff) settings are established and work fine from that point forward. A simple question "Would you like to apply User-Default customization settings to this database?" might be asked when a database is opened the first time in version 8. I think it also happens when a new database is started. That way, the user who assumes all the (ff) settings will be functional in every database that is opened will have that condition. It is assumed that the (gbl) settings will be used in every database for the user.
The second part of this solution would require a time-flag to be set for each database that indicates the last date/time the User-Default settings were saved for each database. A blank time would indicate that the user has not saved User-Default settings for the particular database and therefore it has the Legacy-Default settings or other customizations but not "saved". Then if a database is opened that has that "saved time" earlier than the last time the user saved settings on any database, the question would be asked again. Otherwise, the user would have to remember to fix the (ff) settings in each database after a change to the a setting in any one of his/her files. Put some thought to it and respond if you think it may have some merit. This is not a major concern but would be nice to have fixed. The single database user will not see any benefit except in the conversion process when the file is opened the first time on a specific computer. Ron Taylor On Wednesday, March 5, 2014 6:36 AM, Brian/Support <[email protected]> wrote: We have many professional genealogists who are keeping files for their research using Legacy? They need one file for each client. With the available localization options at the file level they can keep each client's data separate. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com On 05 Mar 2014 5:25 AM, Jenny M Benson wrote: > On 05/03/2014 10:07, Genealogy wrote: >> Can someone please explain why there are two levels of customisation? >> snip >> > I would have thought it was obvious. It gives the user the option to > have different settings for different family files if that's what suits > them. Those that want everything the same can select the same options > for all files. > > I may be quite wrong, but I wouldn't have thought there were that many > users who keep very many files current. > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
