Jump to content


Sonapm

Member Since 04 Apr 2005
Offline Last Active Oct 23 2017 05:48 PM
-----

Topics I've Started

Can't remove blank "child" record

19 October 2017 - 04:53 PM

Help!

 

I have somehow attached a blank "Child" record to a family and I cannot delete or unlink it from my database. It actually shows Sex as "M". When I double click it, nothing happens, either in Family view or Descendants view. When I select it and try to unlink or delete it, I get a message that I need to select a person on which to perform that action. When I highlight it and select "Pedigree," a blank pedigree chart appears saying, "+ Click to add a person".

 

In addition, the following person, along with an apparent Record #, appears in my Index of persons: [UNKNOWN], [Unknown]-180628128. I'm not sure whether this record is the same as the one described above, but it displays a nearly blank line that identifies its Sex as "M".

 

How do I get rid of this "person"?

 

Addendum: I went back and Restored my database from several Backups. I found that the last 4 or 5 Backups include the [UNKNOWN], [Unknown]-180628128 person. The most recent one that did not include it was my backup from 10 Oct 2017.


FamilySearch Person Tools won't replace facts in RM7

29 August 2017 - 08:51 PM

When I match a person in my RM7 database with someone in FamilySearch, I find many facts in their database that I want to download into RM7 using the FamilySearch Person Tools feature.

 

However, I have discovered that if I select a fact and choose to "Replace in RootsMagic", it's actually added to my person as a NEW fact. The existing fact remains; furthermore, the Person Tools window doesn't show this. In fact, it still displays the existing fact, leading me to question whether I actually succeeded in transferring the new fact. It's only when I back out and pull up that person's Edit Person window that I see the new fact as an addition.

 

Can someone explain this to me? Is this a bug, or perhaps some sort of built-in safety net to avoid loss of data? It would seem to eventually, and unnecessarily, over-inflate the size of the database.