Legacy LVUG Community

I have tagged all the individuals with the surname Smith in my database. Now I want to tag all the spouses for those individuals. How do I do that?

I recently uploaded my Legacy data to an Ancestry tree, just to see what works, what doesn't, etc. I'm looking for ways to share all my hard work. What didn't work was all my notes - general, research, event notes, etc. They do not appear with any of the records displayed in the Ancestry tree. I used the Ancestry upload feature within Legacy. I note that when it creates the file, there are no "customize" options that occur with normal Gedcom exports, but the resulting file was a normal Gedcom and all the Note codes with Note texts were there. They just do not get picked up by Ancestry when it translates the data. Has anyone figured a workaround? (This is probably all explained somewhere important - but I haven't come across it yet. :) I realize Ancestry would rather you build your tree on their site, but I prefer Legacy...)

Bob Thompson: Cannot add a comment to your last post for some reason. Reinstalling Legacy should help. For more details go to the Legacy website. Right click on Help Center and select Troubleshooting help, then select Error Messages and Problems. You'll find Error 530 down the list. Hope that helps.

Just for info. I submitted a trouble ticket recently that has now been confirmed as a bug and will be fixed in some future update. Merging or deleting individual records that share events with others can cause a record not found error and could crash with a run-time error - and continue to crash on reopening. It doesn't necessarily occur when the recipient of a shared event is merged or deleted - but it does when it's the primary person. Temporarily un-sharing is a workaround. In any event - back up your data before merging or deleting in these cases - not just a merge backup, but a full database backup and it's useful to check/repair and compact after the merge or delete. This may not occur every time - but you could be caught with an unworkable database if you aren't careful.

Follow up to the Geo database issue.  Thank you for your efforts Tessa Keough JL Beeken     I managed by trial and error to find the solution.  The image below shows the section of the Geo country codes file pertaining to the US.  You will see one entry called USA|+United States.  I changed United States to USA so it now reads USA|+USA.  Now, when I enter a new location into the Geo database in Legacy, the default is USA.  The file is called GeoCountryCodes.txt.  According to Legacy Help, it should be in the Legacy Program folder under GeoDB (on my Mac, it installed in the LegacyFamilyTree folder under _AppData, then Misc).  A simple file search should locate it, wherever it is.

How do I set the default wording for a Geo Database location to USA instead of United States?  The image below shows what came up when I searched the geo database for Rockport, USA.  I can amend the "United States" to USA manually every time, but I'd like to avoid having to do that.

How do I set married surnames so they are in block caps and not between 'slashes'?  The image below will show what I mean.  Across the top (and everywhere else), surnames display in block caps but in the Married Names box near the bottom of the image, they are 'slashed'.  My default for display names is block caps.  Legacy 8, latest build.

A question on copying source documents. Just curious how others do it. When faced with, say, a double page image from a parish register with maybe 10+ different records on it, do you copy the entire page into Legacy so you can retain info on the page number, surrounding records, maybe a parish indicator off to one side, or do you crop the image to give only the target record? I realize there will be a difference in size for the image file, but is that the main consideration?

+Leslie Wright Bagwell - regarding FROM dates in events.  Here's how I fixed that.  I edited the [Date] field in the event definition screen to read [onDate].  Also changed the [Place] field to read [inPlace].  Here is a shot of my Event Definition screen for census events and the resulting sentence at the bottom of screen.

Legacy has some tremendous search capabilities for people records in countless variants, which are enhanced by the use of tags, etc. But one of the major failings in my opinion is the ability to search Locations. Adjusting place names is part of my "do over". I want to search the Location List for certain words/names. I am not talking about finding what records/people use a location with a given word. I want a simple list of all the locations that contain that word. I'll use Washington as an example. It can appear as a state, a county, a township or a city and maybe a few other things. But you cannot easily search for all the place names with the word Washington and see those places in a handy list. Maybe you'd like to change the name of one or more of them to Washingbury, or whatever suits your fancy. The Find window on the Location List only works with the Sort selection you have established - it won't find a word anywhere in the place name. ...

Saw this on Twitter and thought it might be of interest to this group. It's a useful explanation of Lumpers vs Splitters -- i.e. how you organize your sources in Legacy. Hope the link comes through properly. http://news.legacyfamilytree.com/legacy_news/2014/12/lumpers-vs-splitters.html?utm_source=Twitter&utm_medium=tweet&utm_content=LUG&utm_campaign=LegacyTip-LumpersSplitters

For info, for Legacy 8 users, if you do a search for a given Marriage Event-Name and you get a "no matches" result even though there should be some, there is a bug that will be addressed in a future update (tagged as issue 5538).  The search apparently fails for all but the "Equals To" condition.  I reported a problem and this was the response.  I'm not sure if it just appeared in update 459 or if it exists for other 8.0 versions.

How can I eliminate the lines: _QUAL, _SOUR, _INFO & _EVID from a Gedcom which includes source details?  The source detail screen says that use of the Surety and source quality info is Optional, but there doesn't appear to be a way to exercise that option when creating Gedcoms.  I've tried eliminating the Gedcom code QUAL and a few other similar codes, to no avail.  Will choosing Generic or Basic Gedcom formats resolve?   By the way, shared events in a Gedcom file create a complete mess.  Until Gedcom catches up to the Legacy feature, it is almost useless for export purposes IMO.