Jump to content


Member Since 20 Nov 2012
Offline Last Active Aug 10 2016 11:23 AM

Posts I've Made

In Topic: Message ' please make sure you entered a legal file name '

22 May 2016 - 02:41 PM

I have never seen anything like this, and I also don't know how to interpret what you're saying, because some detail appears to be missing.


Can you see whether the complaint is about the name of the GEDCOM file? Does RM mention the name in the error message? Can it be the name of a media file listed in the GEDCOM file itself? Is anything imported at all?

In Topic: Family Search doesn't copy birth place name

22 January 2016 - 10:46 AM

The old subject is still there, in fact, it shows on the bottom of my screen, and FamilySearch is right. It is a RootsMagic thing. I'm using RootsMagic Essentials here, meaning that I can't actually perform a WebSearch, but the RootsMagic screen that I can see suggests that only the person's names and a date range derived from birth and death are used for the search. I assume that, because those are the fields that I can see and edit on screen, in RootsMagic itself. And I think that RootsMagic works right, because adding a birth place to the search right away may limit the search results too much. Besides, why would you expect RootsMagic to search on birth place at all? There's other places, like marriage, residence, and death, that may be just as relevant.


Note that when you use a word like copy or transfer, people will assume that you're complaining about the exchange of data between your tree and the one on FamilySearch, which works right. The real issue is that they probably never understood that you were complaining about SEARCH. It's only now that I read WebSearch in your new message, and see the FamilySearch RECORD Search screen on your site, that I know what you're complaining about. You did not mention that earlier.

In Topic: Some data elements not passed over to FS

09 January 2016 - 01:23 PM

I have never seen birth places being omitted on upload to FamilySearch, but it may seem that way if you upload a place name that can't be verified. I never tested that, but it may help if you can give an example.


Spouse and parents are never copied automatically, because FamilySearch doesn't want you to upload a lot of persons with one click. They want you to check if the person already exists, and to sync data if that is the case, and RootsMagic follows their wish by only allowing you to add one person at a time, and warning you to check for matches first.


As a user, I agree with FamilySearch here. There are loads and loads of duplicates, and some are quite difficult to remove.

In Topic: Importing GEDCOM file breaks some links

15 December 2015 - 04:26 AM

In yesterday's column on FTM at http://www.tamurajon...TreeMaker.xhtmlTamura Jones reported that FTM has been known for messing up trees, and if he's right, what he most times is, the GEDCOM exported from FTM may indeed have an odd link that RootsMagic doesn't understand, or which may even be totally wrong, and incomprehendable for every other program in the world.


To figure out what is the case here, you need to identify the individuals who had broken links, preferably by ID, and have a look at the GEDCOM file itself, to see whether the proper family links are there. You may attach it to a bug report here, so that RootsMagic staff can check whether it's OK or not.

In Topic: Error HTTP/1.1 403 Permission denied

26 June 2015 - 06:39 AM

FamilySearch makes several software changes a day, so it looks like they are causing this. I don't get errors in Ancestral Quest, so it looks like RootsMagic is retrieving information in another way, which worked, but suddenly doesn't.


Can you see details about the error? I can't enlarge the error window here, but it might help if someone can retrieve the full error text, and send that to FamilySearch for an answer.