OK, just in case someone else wants to find and fix something like this. Here's what I did. 1) I renamed the bad location "testing". Any distinctive name would be fine. 2) I exported the entire database into a Gedcom file. 3) I then used Find to locate each instance of "testing". 4) I chose a nearby label and used find to navigate around the gedcom so I could figure out what should have been there--i.e. if I were to delete it, how could I make it look "proper" to Legacy for a re-import? I also made sure I knew which family/individual "owned" that bad location. I made my fixes and saved the gedcom under a new name.
At this point, I imported the revised gedcom into a clean file with fresh RINs. Another option might be to use the "ownership" information to make corrections in the original database. The problem wasn't that the marriage events wouldn't show up. I was chasing a wild goose with that idea. It did have something to do with the data being imported and/or merged. If I ever talk the programming team into adding me to the group, maybe I'll learn enough to be able to figure out just *why* Legacy was getting so confused! And Tom-- Merging the locations will eliminate the existence of the "bad" location--but it won't get rid of the phantom link! If you ever deleted all cases of the new location--you wouldn't be able to! Which means...lots of us are running around with phantom location links in our databases, but we never see them, so don't notice. And while those phantom links may not bother *us*, they may be a factor (or possibly not) in some of the other data-hiccups Legacy has had. Coleen Christensen [EMAIL PROTECTED] http://worldconnect.rootsweb.com/~ccmcconnell/ http://worldconnect.rootsweb.com/~ccslessor/ http://worldconnect.rootsweb.com/~ccwolpoldt/ http://worldconnect.rootsweb.com/~ccchristensen/ ----- Original Message ----- From: "Tom Montgomery" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 01, 2003 5:25 PM Subject: Re: [LegacyUG] Can't find bad location to fix Now I understand what you are talking about! I have several locations in this category. For some reason the location is not attached to any individual but Legacy is confused and thinks it is. I have not done anything about the problem as it does not really bother me. My suggestion would be to merge the bad location into a good location (one that has just one specific individual for that location), run a list and see what you get.....the 'bad' location should be purged. Tom...... Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
