Re: [LegacyUG] Removing Temple Data

2015-05-01 Thread Sherry/Support
Ordinance information on non-living is not really that confidential.
If you look at the Sample file with the LDS option enabled, you'll see
that in Geoff's file. Anyway, there's no problem with sharing that
data.

With LDS option disabled, that option will not be included in reports
and web pages and consequently no LDS information will be included.

If you wish to send a gedcom, in the Gedcom Export window, click on
the Customize button and deselect the LDS Ordinances in the Groups of
items to exclude from export

Oh wait! I Just thought of an easy way to remove the LDS ordinances
from your file. Go to File  Export and select to Export to a new
Legacy Family File. On the Legacy Export window, select Exclude LDS
Information and then create the new file.  You will need to name it
differently. Go over it to make sure everything looks good the open
your other file in Legacy and go to File  Delete File (you might want
to back up first - File  Backup File, just in case).  Then open
the new file and go to File  Rename File to give it the same name as
your original file, if you wish.

The only consequence of the export will be that all the data will show
the date added and modified as the date of the export.



Sincerely,
Sherry
Technical Support
Legacy Family Tree


On Fri, May 1, 2015 at 8:10 AM,  britton...@comcast.net wrote:
 Sherry and Mike,

 Mike, thanks for your reply, but the files already passed though Legacy 
 versions prior to 7 with no indication of LDS content, so likely no tools re. 
 such. I do have Win 2k and XP CDs, but files go back to 98 and 95 days, and I 
 have no equipment with compatible drivers etc. for any. I considered 
 emulation under linux, but no longer have the quality of support needed to go 
 that route again.

 Sherry, thanks too, but the problem is passing the files on. I'm not too 
 picky about my personal use. I downloaded and worked with IGI data on a 
 county wide basis when it wasn't supposed to be possible, but if I know files 
 may have LDS content, it's clearly unethical to pass them on. I use may, 
 because it's also possible that there is none, just erroneous reporting of 
 errors by 7.5.

 I'm pursuing this because other Legacy users may need to look way back. One 
 reason that I do is recent advances in atDNA matching. Present database 
 searching is set up to principally search by known names. Match searching 
 within atDNA and mtDNA databases produces names which are mostly collaterals. 
 Old, early research seems to be rich in fragments or small trees collected 
 because of proximity or other reasons, but never connected to the family 
 tree. It's a source of collateral names with likelihood of DNA matching, not 
 useful to me, but potentially very valuable to others. Another reason is lost 
 data. An example is my PlymtreePratt file. That contained much information 
 from the OPC, presumably now dead, including early births. Work stopped about 
 2002, because there was no film or other access to parish records for 
 neighbouring Broadhembury. Those BMD records became available last December, 
 when Devon BMD came online, removing the brick wall. Plymtree early births 
 were missing there though, so may now be lost.

 kb


 - Original Message -
 From: Sherry/Support she...@legacyfamilytree.com
 To: legacyusergroup@LegacyUsers.com
 Sent: Thursday, April 30, 2015 2:50:36 PM
 Subject: Re: [LegacyUG] Removing Temple Data

 If you're not LDS and don't want to see the LDS information, just go
 to Options  Customize  General tab and deselect the LDS display

 It will still be in your file and a heck of a lot easier than trying
 to remove what's there!




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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



Re: [LegacyUG] Removing Temple Data

2015-05-01 Thread brittongen
Sherry and Mike,

Mike, thanks for your reply, but the files already passed though Legacy 
versions prior to 7 with no indication of LDS content, so likely no tools re. 
such. I do have Win 2k and XP CDs, but files go back to 98 and 95 days, and I 
have no equipment with compatible drivers etc. for any. I considered emulation 
under linux, but no longer have the quality of support needed to go that route 
again.

Sherry, thanks too, but the problem is passing the files on. I'm not too picky 
about my personal use. I downloaded and worked with IGI data on a county wide 
basis when it wasn't supposed to be possible, but if I know files may have LDS 
content, it's clearly unethical to pass them on. I use may, because it's also 
possible that there is none, just erroneous reporting of errors by 7.5.

I'm pursuing this because other Legacy users may need to look way back. One 
reason that I do is recent advances in atDNA matching. Present database 
searching is set up to principally search by known names. Match searching 
within atDNA and mtDNA databases produces names which are mostly collaterals. 
Old, early research seems to be rich in fragments or small trees collected 
because of proximity or other reasons, but never connected to the family tree. 
It's a source of collateral names with likelihood of DNA matching, not useful 
to me, but potentially very valuable to others. Another reason is lost data. An 
example is my PlymtreePratt file. That contained much information from the OPC, 
presumably now dead, including early births. Work stopped about 2002, because 
there was no film or other access to parish records for neighbouring 
Broadhembury. Those BMD records became available last December, when Devon BMD 
came online, removing the brick wall. Plymtree early births were missing there 
though, so may now be lost.

kb


- Original Message -
From: Sherry/Support she...@legacyfamilytree.com
To: legacyusergroup@LegacyUsers.com
Sent: Thursday, April 30, 2015 2:50:36 PM
Subject: Re: [LegacyUG] Removing Temple Data

If you're not LDS and don't want to see the LDS information, just go
to Options  Customize  General tab and deselect the LDS display

It will still be in your file and a heck of a lot easier than trying
to remove what's there!




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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



Re: [LegacyUG] Removing Temple Data

2015-05-01 Thread brittongen
Thanks, Sherry, for the ordinance guidance, and I had not thought of exporting 
in native mode, which avoids side effects from gedcom use. That should work 
fine. If AFN numbers are stripped, that's not a big issue, and I'll keep backup 
with them. Thanks also, Brian, for alerting me to that.

kb





Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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


Re: [LegacyUG] Removing Temple Data

2015-05-01 Thread Sherry/Support
The AFN numbers wouldn't be stripped. That's not part of the Ordinance data.


Sincerely,
Sherry
Technical Support
Legacy Family Tree


On Fri, May 1, 2015 at 9:20 AM,  britton...@comcast.net wrote:
 Thanks, Sherry, for the ordinance guidance, and I had not thought of
 exporting in native mode, which avoids side effects from gedcom use. That
 should work fine. If AFN numbers are stripped, that's not a big issue, and
 I'll keep backup with them.  Thanks also, Brian, for alerting me to that.

 kb





Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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



[LegacyUG] Removing Temple Data

2015-04-30 Thread brittongen
We use 7.5 De Luxe and Win 7. I recently needed files from 8 to 15 years back, 
finding some apparently archived in 2007 in Legacy native format, versions 5 or 
6. Several appeared to convert successfully to 7.5, navigation OK to material 
of interest, but when I ran file repair prior to use/merge, Temple data errors 
were reported, plus a list of Temples. I assume that I was originally given the 
files as PAF gedcoms, and the LDS content propagated quietly until it reached 
7.5. I'm not LDS, so it's information that I should not have, and certainly 
should not pass on. Is there a convenient way to delete or remove it? The 
numbers are in the low thousands, so even making new gedcoms and using a text 
editor isn't real appealing unless find-and-replace-all could be used to 
quietly disable the relevant tag(s).

The advice here:
http://support.legacyfamilytree.com/article/AA-00385/11/Error-Messages-Problems/Fix-This-Temple.html
requires that I revert to an earlier file version without the problem. None 
available. Repeated repair cycles do seem to clear the problem, but presumably 
valid Temple data may remain.

kb




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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


Re: [LegacyUG] Removing Temple Data

2015-04-30 Thread MikeFry
On 2015/04/30 18:46 PM, britton...@comcast.net wrote:

 We use 7.5 De Luxe and Win 7.  I recently needed files from 8 to 15 years
 back, finding some apparently archived in 2007 in Legacy native format,
 versions 5 or 6.  Several appeared to convert successfully to 7.5, navigation
 OK to material of interest, but when I ran file repair prior to use/merge,
 Temple data errors were reported, plus a list of Temples.   I assume that I
 was originally given the files as PAF gedcoms, and the LDS content propagated
 quietly until it reached 7.5.   I'm not LDS, so it's information that I
 should not have, and certainly should not pass on.  Is there a convenient way
 to delete or remove it?  The numbers are in the low thousands, so even making
 new gedcoms and using a text editor isn't real appealing unless
 find-and-replace-all could be used to quietly disable the relevant tag(s).

My suggestion would be to download and install a much earlier version of Legacy
and use that to turn the Temple stuff off. Then, the saved file (hopefully
without Temple) could be read by a recent version of Legacy and hopefully there
will be no Temple data in the file.

--
Regards,
Mike Fry (Jhb)




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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



Re: [LegacyUG] Removing Temple Data

2015-04-30 Thread Sherry/Support
If you're not LDS and don't want to see the LDS information, just go
to Options  Customize  General tab and deselect the LDS display

It will still be in your file and a heck of a lot easier than trying
to remove what's there!

Sincerely,
Sherry
Technical Support
Legacy Family Tree


On Thu, Apr 30, 2015 at 9:46 AM,  britton...@comcast.net wrote:
 We use 7.5 De Luxe and Win 7.  I recently needed files from 8 to 15 years
 back, finding some apparently archived in 2007 in Legacy native format,
 versions 5 or 6.  Several appeared to convert successfully to 7.5,
 navigation OK to material of interest, but when I ran file repair prior to
 use/merge, Temple data errors were reported, plus a list of Temples.   I
 assume that I was originally given the files as PAF gedcoms, and the LDS
 content propagated quietly until it reached 7.5.   I'm not LDS, so it's
 information that I should not have, and certainly should not pass on.  Is
 there a convenient way to delete or remove it?  The numbers are in the low
 thousands, so even making new gedcoms and using a text editor isn't real
 appealing unless find-and-replace-all could be used to quietly disable the
 relevant tag(s).

 The advice here:
 http://support.legacyfamilytree.com/article/AA-00385/11/Error-Messages-Problems/Fix-This-Temple.html
 requires that I revert to an earlier file version without the problem.  None
 available.  Repeated repair cycles do seem to clear the problem, but
 presumably valid Temple data may remain.




Legacy User Group guidelines:

http://www.LegacyFamilyTree.com/Etiquette.asp

Archived messages after Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyusers.com/

Archived messages from old mail server - before Nov. 21 2009:

http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

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