Family Historian User Group

About £250 on Amazon, so entry level. Spec looks very similar to my old laptop, which runs full W10 on a Pentium with 4 GB RAM and a small SSD. Runs well for FH and basic MS365 & web, but I wouldn’t render HD video on it! Small SSD might be the limitation (128 GB), but fine with cloud storage.

Simple enough for the OP to check the first step when he’s back on line. Does “Check for updates” do anything or not? Agree though that plenty of other things will eventually stop working in even a fully patched W7, not just FH.

Agree - it's not viable to update manually, but all I was questioning was whether the automatic W7 "Check for Updates" menu option still works to restore the PC to the latest (obsolete) W7 configuration. I don't know whether MS have deactivated that for W7 or not, but it continued to work in XP long...

Obviously no new updates have been produced for ages, but are you sure that old ones have been withdrawn? I’ve never tried it with W7, but I had an old standalone XP box that I could reinstall from an old CD and update online well after the end of official support. Edited to add that I wouldn’t see ...

Welcome to FHUG, Curtis.

A good place to start is the video cited in this thread.

Be aware that FH handles sources slightly differently to many other popular apps, so it may take a bit of getting used to if you are used to working a particular way in another app.

As an aside to reporting a minor bug with date formatting in a different context, I asked CP about supporting this ISO 8601 date format within FH, as it is the international standard for text representation of date in computer systems, and the only common format that sorts chronologically as text. T...

Excellent - if there is only one GEDCOM 7.0, that simplifies things enormously. All we are doing is making sure we are using the latest description of it.

My point was a general one, rather than directed at today's latest flavour. This thread will be kept up to date with the latest version of GEDCOM 7, and we only raise issues against that. CP will be aware of the updates, and they will make up their own minds about if/when to make corrections. Is it ...

It's largely academic unless the source and target apps use precisely the same version, but note that the link Jim posted notes Simon Orde (the creator and godfather of FH) as a contributor and recipient. I think that directs us to review against the latest release, as CP will be fully aware of it, ...

To expand a little on Mike's comment, I believe that FamilySearch would like their FamilySearchID to be a truly global UUID that identifies one individual uniquely on all systems. IMO, that is totally impractical, and the UniqueID field used by FH and a number of other apps (and now built into GEDCO...

My comment was a little too brief. Using the command or plugin, only certain fields will update after it is run. With a Query, all changes to listed fields are updated in real time. Neither of us know exactly how Bill has structured his sources, so I have no opinion on which is the preferred option ...

You can do the same thing directly from the View > Citations to Source Record menu option in FH7 if it’s easier. However, neither the plugin or menu option update dynamically, unlike a Query.

Another option is to display the new split sources in a Query. For example, if you are splitting the 1940 census, and you know each citation is linked to at least the census Fact, you could tabulate individuals, 1940 census, and source (assuming it is the first/only source). Work down the list, amen...

Bill, The plugin help describes how citation equivalence is determined and how the split source name is derived. Essentially, the individual (with a small i) Where within Source values (or selected Templated Source field values) are appended to the original lumped source Title and Short Title. From ...

If you are happy with the splitter way of working, take note of Jim's comment above, and try out the Lumped Source Splitter plugin. It was developed primarily to help users of RM and FTM (which both have a stronger bias towards lumping) convert their sources to the preferred FH splitter format.

UID already reported as "GEDCOM 7 error for UniqueID #701514"

It also exports UniqueID in the old format of _UID rather than the GEDCOM 7 version of UID. When this is corrected in a text editor and reimported as a new project, UID is reported as a UDF. :o Disappointing there are so many obvious errors in an app that takes GEDCOM compliance as a major feature, ...

Thanks Nick - nicely paced and clearly explained. There is definitely a place for this type of walk through of up to date features to get users started. Spoiler alert - it strongly promotes the "Splitter" model for anything other than simple sources such as GRO Indexes, so the detailed explanation o...

Rant alert - help text should be written in plain English for everyday users, not written for geeks in geek language!

I had a quick read through of the Standard Fact Set file, and the only words that I noticed were naturalised/...ized and baptised/...ized, so a US fact set will be easy enough to do, and certainly easier than wrestling with creating a Language Pack. I was inconsistent with the Ancestry sync plugin o...

OK, thanks. I've already implemented a simple B/M/D export option, as it was just a few new lines of code, but tidying up names is a bit more work. It's worth doing though, as the reworked name tables are a more elegant solution. Inevitably, I think of better ways to do things as I get more familiar...

There is a flip-switch of sorts in Tools > Preferences > International, where the Display Language can be flipped between UK and US English. However, it's not clear how far that affects what the user sees. The only difference I noticed was changing between Color and Colour in the Preferences > Displ...

Up until about the mid-20th century, I've stayed with the Ancestry images. Where there is a colour cast or grey background, this is easily removed with IrfanView to give a neater appearance in reports. Mid-20th century is a mix, but later Ancestry images seem to be relatively poor by comparison with...

No problem. I've just changed my settings and deleted all my ThumbCache.data files apart from the one under the ProgramFiles(x86) folder relating to the master copy of the Sample Project, so I'll monitor performance over the next few days and weeks.

Thanks both - I’d forgotten the cache options in Preferences, so that does seem to do what I was seeking. I’ll follow David’s route and check that it does not reappear.