Jump to content


ian.baker

Member Since 05 Jan 2016
Offline Last Active Jan 08 2016 11:58 PM
-----

Posts I've Made

In Topic: FTM & RM 7.0.10.0

06 January 2016 - 10:20 AM

I hope this reply is in the right place - it is for Laura.

 

I have a large FTM media folder with JPG files of all pages I cite in all censuses, parish records, electoral roles etc - nearly 4,000 JPGs.

RM import correctly points to each JPG - which impressed me.
I have edited each JPG to include the "FTM Person number" of all relevant people. So a single JPG Census return page will have all members of one, or more, families listed and along side them their Person ID/Record Identification Number. Generally 1-10 numbers added to each JPG.

This is not a paper file which has been annotated but the demand is similar.

Changing all the annotated JPGs would not only be a very long task it would be difficult to ensure accuracy as the numbers are integrated into the image and not searchable.


In Topic: FTM & RM 7.0.10.0

06 January 2016 - 12:38 AM

As a disgruntled FTM 2014 user I have looked to RM 7.0.10.0 as an alternative but the import of FTM Gedcom to RM is broken.

 

The issue is the feature that FTM calls Person Id number and RM calls Record Identification Number.

If a person is deleted, or two merged, in FTM then a gap correctly appears in the Gedcom number sequence exported by FTM, but when imported by RM the number sequence is remade with no gaps hence all person id numbers/record numbers after the first gap will be wrong.

RM Support has confirmed this is how RM currently works when importing a Gedcom file from an application other than RM. Curiously they say that importing from FTM 2006 (or earlier) or from RM does enable an option to keep the original number sequence - so why not fix the import from FTM 2014....

 

With over 4,000 records a manual edit is not viable - so am I stuck with FTM?


In Topic: Importing GEDCOM file breaks some links

06 January 2016 - 12:26 AM

As another disgruntled FTM user I have looked to RM 7.0.10.0 as an alternative but the import of FTM Gedcom to RM is broken.

Posted on this thread as it directly links to Gedcom import but not SQL.

 

The issue is the feature that FTM calls Person number and RM calls Record Identification Number.

If a person is deleted or two merged in FTM then a gap correctly appears in the number sequence exported by FTM, but when imported by RM the number sequence is remade with no gaps hence all person id numbers/record numbers after the first gap will be wrong.

RM Support has confirmed this is how RM currently works when importing a Gedcom file from an application other than RM. Curiously they say that importing from FTM 2006 (or earlier) or from RM does enable an option to keep the original number sequence.

With over 4,000 records a manual edit is not viable - so am I stuck with FTM?