The semantics of Windows' READONLY bit on files is not the same as Linux' Immutable attribute (immutability on Linux requires 'root' to set/unset) -- i don't know if there's a true equivalent. So, i'd suggest that given that you have no control over Legacy's insistence that it erase the READONLY bit [1], that you try to use elevated privileges (another account at least) to set ACLs on the file(s) in question to allow READ by Everyone (or those in question), but only allow full-control by an elevated account. You may have to use TAKEOWN to make the files owned by an elevated account. (or just try copying your database into another account's
Once you've done all this, i bet you will run into Legacy fatally faulting and exiting, however (which is why i'm not bothering to test the validity of my theory). I suspect the engineers have made the assumption that they MUST have write access to the file, and there's either deliberate code conditionals that gracefully exit the program, or ungracefully take an exception. I don't know if there are restrictions on mention of other vendor products on this list (etiquette #2 is just seems advisory), and i have no direct experience, but you can find products that can take GEDCOM and create directly runnable EXEs or do view only of GEDCOM data. google: "gedcom view-only". (yes, i do know that GEDCOM interchange is lossy) Anyway I will +1 the idea that Legacy should have a View-Only mode. (preferably selectable as a field value inside the Access database with associated UI controls) --stephen [1] IMHO, this behavior (silently altering filesystem metadata for objects that are normally user-controlled ) is bad practice. the program should issue a warning or error message that it can not proceed due to the files being READONLY . (In a Perfect World...). I do, however, understand the "lowest common denominator" user-targeted programming model that's common on Windows and the "support overhead" arguments being made in this thread -- but I'm an advocate for at least having "Advanced User" modes that can be enabled where sensibility takes over again. Don't know how much engineering changes would need to be made to the program to support a VIEW-ONLY mode. On Fri, Mar 13, 2015 at 12:24 PM, Brian/Support <[email protected]> wrote: > Legacy has no option to prevent changes to files. > > Brian > Customer Support > Millennia Corporation > [email protected] > http://www.LegacyFamilyTree.com > > On 13/03/2015 12:46 PM, GeoPappas wrote: > > Is there any way to make a family file read-only within the application? > > > > I have created a family file that I would like to prevent from getting > > changes. > > > > > 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://support.legacyfamilytree.com > > 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 > > -- Stephen Dowdy ([email protected]) 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://support.legacyfamilytree.com 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
