Jump to content


Member Since 04 Apr 2004
Offline Last Active Yesterday, 02:58 PM

Posts I've Made

In Topic: Corrupted Tree

05 October 2018 - 06:39 AM

I imported a Gedcom file of the tree and I was hoping that RM7 had some utility to identify these orphaned branches so I can re-link them to the main tree and repair the damage.


Additionally, you can check the file folder where your RM database is... for a .LST file (with same naming as your database) that gets created during import (if RM has any issues with the .GED file) that would contain data that didn't make it into the database.

In Topic: Delete multiple families and their descendants

30 September 2018 - 10:43 AM

Here's the longest but perhaps most robust approach (ie. non-Drag 'n' Drop):

1. Import the GEDCOM (from others) into a fresh empty temporary RM database "A", unlink (from the main tree) the person (or persons) that connect(s) them, their family and descendants to that main tree, and then Export a GEDCOM as follows:
a. Click upon and highlight any person in the desired tree that you've just adjusted.
b. Now choose File->Export->People to export->Select from list->Mark group->Everyone in the highlighted person's tree
c. In the Mark group dialog window, click the checkbox to the left of the highlighted person's name and then choose <OK> button
d. Having been returned to the GEDCOM Export dialog window, click the <OK> button there to initiate export of desired tree to a new GEDCOM


2. Import the newly-created GEDCOM (from your edits) into *another* fresh empty temporary RM database "B",. Normalize all the data via edits and merges to match the conventions used in your Master (or Destination) database for Surname, Nicknames, Suffix/Prefix, Date Formats, Place Names, Fact Types & Descriptions (along with associated Sentence Templates and Witness Roles), Source Formats, ETC.


3. Repeat steps 1a thru 1d ...to Export a "normalized" GEDCOM ready for import to your Master (or Destination) database.


4. Backup your Master (or Destination) database in preparation for importing this newly-created GEDCOM (in case something goes wrong).


5. Import the "normalized" GEDCOM to your Master (or Destination) database, perform all the Tools->Merge functions, check that imported tree is properly linked, and examine the final results for desired completeness. Consider performing additional backups prior to each operation that might potentially change a swath of your tree(s) and data.


6. Delete temporary databases "A" and "B" when a satisfactory outcome is achieved.


NOTE: Whenever a GEDCOM is imported to a RM database, if RootsMagic encounters *any* issues with that import... it will create a .LST file (text) in the same folder as the destination database... listing any data that it had a problem importing.

In Topic: Compare files doesn't work

25 September 2018 - 09:23 PM

You might want to experiment with sqldiff.exe https://www.sqlite.org/sqldiff.html

In Topic: RM not exporting place geocodes in gedcom

04 September 2018 - 04:51 PM

Does anyone have any ideas why and how to turn it back on?

I believe they are always exported as long as Extra Details (RM Specific) is checkmarked
on the GEDCOM Export dialog screen

In Topic: please increase the range of acceptable years in Sort Date

29 August 2018 - 07:26 AM

By the way, 2^64 = 18,446,744,073,709,600,000

Looks like Delphi's largest number representation is a LongWord UInt64 which has a range from 0 to 18446744073709551615