on this renewal problem.
Howard Cady
From: Michele Lewis
Sent: Thursday, May 9, 2019 5:19 AM
To: 'Legacy User Group'
Subject: Re: [LegacyUG] Please forget that previous post.
Normally I wouldn’t comment on anything MyHeritage but I will this time. Legacy
is a completely separate entity. MyHeritage’s
everyone without death information to
living and then use Advance d set living to set obviously deceased people to
dead.
Cathy
Howard Cady wrote:
Cathy,
Somewhere in the help listings for Legacy I found a method for
resetting the Living Yes/No for a tagged set of individuals. I used
ion screen - it would
reset to deceased if one of the fields associated with death was filled.
Cathy
Howard Cady wrote:
Cathy,
You were correct as to the cause of my problem (individual marked as
deceased). Fi xing the problem was harder. The “View-Set Living” reset
kept return
Sources was my final
fix that was required to get him alive. Thanks for steering me to the solution.
Howard Cady
From: Cathy Pinner
Sent: Saturday, November 4, 2017 6:55 PM
To: Legacy User Group
Subject: Re: [LegacyUG] Potential GEDCOM Error
Howard,
You don't need LTools for this and I'd
in death or burial field or adding a
source to them will switch the Living indicator. Removing it doesn't switch the
indicator back.
Cathy
Howard Cady wrote:
I used Legacy 9 version 198 to prepare an GEDCOM (import to Ancestry
version) of my wife's bloodline (only her relatives) with privacy
living descendants were properly exported as names only. A deceased older
sister was properly exported as deceased. Have others noticed this potential
error?
Howard Cady
--
LegacyUserGroup mailing list
LegacyUserGroup@legacyusers.com
To manage your subscription and unsubscribe
http
Michele,
Thanks for posting the "Tip of the Day" I am one of the non FaceBook users
of Legacy FT. This tip makes me want to see your previous Tips. I hope you
will be able to do this and continue to cross post to the Legacy Users
Group.
-Original Message-
From: Michele/Support
PicName
= If.jpg (a document file) as is used when PicName = Is.jpg (a sound file)
or when PicName = Iv.jpg (a video file). That should take only one
additional "Else IF" statement.
Howard Cady
-Original Message-
From: dwquig...@cox.net
Sent: Friday, February 12, 20
to have a test for the number of characters being downloaded so that it can
decide to put short descriptions (less than 255 characters into
tblER.Description) or long descriptions (more than 255 characters into
tblER.Desc – a memo field)
Howard Cady
From: KenMcGinnis
Sent: Tuesday, July 28
My OS Windows 8.1, 32 and 64 bit computers, Legacy version 8.0.0.499 setup
to connect to LDS FamilySearch with remembered name and password.
Some individuals in the LDS FamilySearch database have under “Facts and
Events” an entry “Life Sketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun
information into Legacy’s Notes, or use
FreeClips to do the same thing. Delete anything in Legacy’s Event Description
field if you plan to access FamilySearch with an individual using this event.
Howard Cady
From: Kirsty M. Haining
Sent: Wednesday, March 4, 2015 1:47 PM
To: legacyusergroup
of this event. (Anything in the Description
field will prevent connection of this individual for further sharing with FSFT)
I do not know which event caused you trouble, but I suspect the same difficulty
with any event that has lots of information in the FSFT description field.
Howard Cady
From
Kirsty,
PS I switched the left and right information on the “Shared information” screen
for Legacy and FamilySearch. Sorry.
Howard Cady
From: Kirsty M. Haining
Sent: Tuesday, March 3, 2015 5:00 AM
To: legacyusergroup@LegacyUsers.com
Subject: [LegacyUG] Switching fields in an event
Hi, everyone
location will cause a location merger even though the Latitude and/or Longitude
differ. The new Lat/Long are discarded in favor of the older existing ones.
If you desire more information, let’s correspond directly – off list.
Howard Cady
From: Paula Ryburn
Sent: Saturday, January 31, 2015 7:11
combine, but I am not using the conventional US 4 place location convention and
I do know that mismatched lat/long entries do not prevent combining. This
might be the cause for others to have unexpected event changes.
Howard Cady
From: Gene Wheeler
Sent: Tuesday, January 6, 2015 10:05 AM
My OS Windows 8.1, 32 and 64 bit computers, Legacy (LFT) version 8.0.0.459
setup to integrate with FamilySearch FamilyTree (FSFT) with remembered name
and password (Option 1.8 checked).
Some individuals in FSFT have under “Facts and Events” an entry
“LifeSketch” e.g. William Scott b.
My OS Windows 8.1, 32 and 64 bit computers, Legacy version 8.0.0.454 setup
to connect to FamilySearch with remembered name and password.
Some individuals in FSFT have under “Facts and Events” an entry “Life
Sketch” e.g. William Scott b. 25 Sep 1801, d. 1 Jun 1880, FS ID# LWQM-F3Q. The
Mike Fry, I suggest playing with LTools and a COPY of the Sample.fdb file.
Generate a twin with your required name order. Then use LTools to change table
IR so that the entry for BirthSD (birth sort date) is earlier for the first
born by a day, but leave the entry for BirthD to be identical
-parents etc.
This allows for keeping people in the correct order and century (or better). I
hope it is not planned to drop this feature.
Howard Cady
From: Geoff Rasmussen
Sent: Thursday, July 10, 2014 9:58 AM
To: legacyusergroup@LegacyUsers.com
Subject: [LegacyUG] Legacy Family Tree - Virtual
files.
Jay
On Thu, Jul 10, 2014 at 9:33 AM, Howard Cady howardc...@q.com wrote:
Goeff, I note in your Webinar notes that “Est = Estimated” has been
dropped from allowed dates. One of the main reasons for my switching to Legacy
was this descriptor. I use it especially when I know
to be listed ahead of French,
German, or American sources, if these latter sources are mentioned at all in
the Research Guidance.
Howard Cady
- Original Message -
From: Michele/Support
To: LegacyUserGroup@LegacyUsers.com
Sent: Thursday, December 26, 2013 8:10 AM
Subject: RE: [LegacyUG] Research
version of Legacy. NEVER work on your original family file with
LTOOLS - only use a copy of your original file.
Howard Cady
- Original Message -
From: Laura Johnson rngad...@madisontelco.com
To: LegacyUserGroup@LegacyUsers.com
Sent: Saturday, October 26, 2013 7:52 AM
Subject: Re: [LegacyUG
this to be a continuing item
as the LDS FamilySearch data base and its preferred IDs continue to be
updated/changed in the future.
Howard Cady
Legacy User Group guidelines:
http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages after Nov. 21 2009:
http://www.mail-archive.com/legacyusergroup
into family Tree directly (on the LDS site) and
try to bring up the 'missing' individual?
Paul Gray
-Original Message-
From: Howard Cady [mailto:howardc...@q.com]
Sent: September-21-13 4:11 PM
To: LegacyUserGroup@LegacyUsers.com
Subject: [LegacyUG] Obsolete FamilySearch IDs
I have noticed
Paul, I can confirm that you are addressing a real concern. I have had the
FamilyTree search function of LegacyFamilyTree v219 change some of my
FamilySearch IDs from say P21X-J6L to say XYZ2-4LQ without any request for
permission or any notification by LegacyFamilyTree when I was using the
Marie,
I'm with you!! (Fields for birth, marr, death, separate fields for dates
(month, Day, Year and places, Location, city, county, state, country)
I am so surprised that these fields haven't already been added !!
I really Hope they are in the next big upgrade!
On
known date.
Howard Cady
- Original Message -
From: Jerry jerrysemailgro...@gmail.com
To: LegacyUserGroup@LegacyUsers.com
Sent: Saturday, March 17, 2012 1:16 PM
Subject: Re: [LegacyUG] Persons with only assumed/acquired surnames
Thanks for those samples, David. What I could not quite
bk and Dennis
This sounds like an important enough problem that the Users Group and Legacy
Support should know the required fix. Please keep us informed. It seems
like the obvious File Maintenance Check/Repair solution should have
been a fix and we need to know why it failed.
hc
- Original
I think this is what you want. Open Legacy and select your file. Then
ViewMaster ListsSourceShow Only and check only Source Writer
boxOptionsPrint etc.
I have tried to reply in text only mode. Will find out soon.
- Original Message -
From: Frank J. Wesslowski
To:
I have been moving a fair sized (over 2 individuals) genealogical
file from Family Tree Maker to Master Genealogist to Legacy via GEDCOMs.
One of the first steps to getting the file in order is to clean-up the
Master Location List. I want to locate places by latitude and longitude and
30 matches
Mail list logo
