Family Historian User Group

Would the RM version be relevant?

That's because the latest version is in the plugin store: https://pluginstore.family-historian.co ... ronization

Insert image is used to insert an image that already exists somewhere on the internet - you enter it's URL between the tags.

You need to attach the photo. Click ATTACHMENTS below where you compose the message and ADD FILES.

Bonus: because other sources are ignored, it doesn't matter if the GRO birth source isn't the first!

I've checked at least 20 cases where from the birth date and combination of sources already present it might have missed them and so far it's looking absolutely spot on.

Thank you.

Mark, A lot of the manual changes I am having to make in RM are where the name has changed (typically where I had something like Fred A Smith and I've found out what the A was for). After the merge the updated name appears as an Alternate name in RM. You have to edit that to make the new name the pr...

Having completed the update I have a better handle on the Living issue. If the only change you have listed is the Living flag, it will be shown in TreeShare as a changed individual, but there is no way to do the update. You MUST use the Show on Ancestry option and check/amend. All the cases where th...

If the only change made in FH (and hence RM) to an individual is to the Living flag, then TreeShare doesn't work. Although the individual is listed in the changed list, there's no arrows to enable the change to be pushed to Ancestry, all you can do is Show on Ancestry and Quick Edit the person. ......

Starting with a fact query is probably best. Is the attached a good starting point for you?

If that works for you, to get your other columns, for example father, you'd use:

You presumably do a select using the UniqueId. As you go through could you check that only returns one row?

Found him! select PersonID, count(*) count from PersonTable group by UniqueID having count(*) > 1 did the trick! Is that a check you could build in the the plugin update - it would detect when the RM merge has failed. The reason for duplicate was that an individual had been recorded with the wrong g...

I'm in the middle of a fairly big update. Having finished making the RM remaining changes I've just rerun the Compare and whilst it lists no individuals it has: FH Individuals: 1785 RM Individuals: 1786 FH Families: 549 RM Families: 549 The Update report doesn't show who the extra RM individual is e...

On your other point, I tend to run a second compare at the end of the process just to check everything has gone through ok. Is that before or after TreeShare? My thought is to make sure everything is correct in RM before starting on TreeShare using the original Update Guide. The update research not...

We can probably go one better than that - by using a similar technique to the Windows backup and restore plugin, it could actively check whether RM is open or not. I wouldn’t force-close it, but I’ll have a play with options. Hmm... I tend in RM to go File, Close File. That means RM is still runnin...

Does adding a column =MediaCount() to the sources tab of the records window help?

Mark,

Having worked through the RootsMagic Update Guide, I've been rerunning the Update to make sure all the changes have been made correctly. Is this safe? If so is it worth recommending?

Mark, could I suggest a small addition to the message box that pops up when you do an update to remind that the RM database should be closed.

I've looked at several of those where the sorting was odd and they all look good now - thank you.

tatewise wrote: ↑

09 Feb 2023 16:25

I've also modified the Field column so that its items can be double-clicked or right-clicked to open the Property Box.

Neat!

I recall asking about this issue or similar a couple of years ago when doing my own birth/death cert (a tabular one) and wanted to know how to get the maiden name. At the time Nick said is wasn't really simple/possible for reasons. I'm not sure if this is still the case. I think it was this thread:...

I've also found that it is missing " husband/wife/widow/widower of [spouse] " from section 6. I'm working on the auto template for that. Inserting the line =IF[{SPOUSE}%=IF[{SPOUSE.DECEASED}%=TITLE[{KEYPERSON.GENDER.WIDOWERWIDOW}]%=TITLE[{KEYPERSON.GENDER.HUSBANDWIFE}]] of {SPOUSE.FULL.CAPS} {SPOUS...

I've also found that it is missing "husband/wife/widow/widower of [spouse]" from section 6. I'm working on the auto template for that.

Just spotted that when recording a death for a married woman, in the autotext generated by Death Certificate 2007- (England/Wales) section 4. Maiden surname of woman who has married it is putting the married surname, not the maiden name.

I looked this morning to see if I could understand what's happening compared with your explanation. It's happening quite a lot - here's one example.

It seems to be wherever I've used the Add GRO Source plugin for a marriage.

Hope I've shown enough for you to look.

The first individual I tried it on had sources for the name as the first and sixth rows.

Just a minor observation: would it help if the rows were sorted by data ref within each individual to make it easier to see where there are multiple sources for a single field.