Family Historian User Group

Many thanks for this Jane, by which I mean your recommendation of PSPad as an editor (but I doubt I'll ever get to grips with all its capabilities) as well as your most useful PSPad extensions for FH Functions, and of course your How-To instructions, which I was able to follow easily once I read the...

I agree with Gerry, above, that to display an Individual's record multiple times in the Records window just because they are known by different names in different contexts or at different times is likely to be too confusing for most users.  For instance my father Kenneth James Richmond was always kn...

There is another Wish-list item which may be relevant: 59 - Address management like that for Places , but to which I added the following comment: I can see why auto-complete and a system like Tools > Work with Data > Places could be useful for the Address field, but I can see several complicating fa...

FH version 4 allows you to output a separate row for each attribute value resulting in potentally many rows per person, provided you use a Fact Query.  I've just uploaded a simple example which may help:
http://www.fhug.org.uk/cgi-bin/index.cg ... ies&id=103

I think this is covered in the Help file page Edit Custom Item.

I thought perhaps the slightly different behaviour on the Families tab is deliberate because unlike all other record types, a family has not one but two identifying (linked) names, either of which may be missing altogether or unknown. This means that the 'appropriate place' is not as obvious as on t...

[oops]Oops! I should of course have emphasized that since it is a Fact Query, it needs at least version 4 of FH.

After a bit of a struggle, I managed to construct a fact query which I think achieves at least some of what you might be after.  I've just added it to the Downloads, and hope it proves useful.[smile]

I just tried saving a diagram, with scaling set to 75%, as a FH chart.  Then I closed and reopened FH and opened the saved chart.  Guess what - the scaling was still 75% BUT the zoom was 77%, which I was not expecting.

Crys, Does the query in version 3 show the Source and the Source Citation columns differently (with the Source having the little scroll at the left), as in my version 4 example?  And do you get the same warning message about record rather than field whichever column you select for the delete?  If so...

I think you need to click on the Show Face button (immediately left of the yellow-arrow Go To Record button).[smile]

I have FH v4.0.2 and can confirm that what Jane said above definitely works for version 4. You can define a query with a column for the Source (the FH default) and a separate column for the Source Citation: Source: %INDI.BIRT[1].SOUR[1]>% Source Citation: %INDI.BIRT[1].SOUR[1]% and the result is as ...

It is a limitation of the GEDCOM standard (with which FH very sensibly complies as closely as possible) rather than of FH per se which means that you cannot attach Multimedia objects to a Note record; (see http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gcch2.htm#NOTE_RECORD ). As you can ...

The GEDCOM 5.5 standard defines a specific tag for Surname-Prefix with the following explanation: Surname prefix or article used in a family name. Different surname articles are separated by a comma, for example in the name 'de la Cruz', this value would be 'de, la'. FH (v4.0.2) allows you to input ...

I registered and used the site with some success before the free days expired.  I've now had two emails from them: Dear Peter, Welcome to WorldVitalRecords.com! As a registered member, you're now eligible to receive 50% OFF a World or U.S. Membership.                   and Hello Peter, We had such a...

This is now much easier because the File > Export option in FH4 can export a GEDCOM file based directly on a Named List, so no need to create a Query or use the Split Tree Helper.

Martin, Source records can be merged using FH directly. The Help file ( Basic Record Merging and Branch Merging ) contains the following: Basic Record Merging can be used to merge records of any type - not just Individual records. For example, you might discover that you had accidentally created two...

Jon,
Yes, I was suggesting adding the two necessary extra columns, but their width on screen can be reduced to near zero, so they needn't waste much space and there need be no visible duplication of data. (I see Jane also suggested narrowing the extra column.)

It is possible to sort the records by surname and first name (and date if required) if that would have the desired effect. Or am I missing something?

Lesley, I found the above quote from the FH Help file by doing a search for 'multimedia date'; it was on the page headed Property Box: Main Tab for Multimedia Records . The same search also finds page headed Edit Media Item which contains the following for the date field: It is a good idea to enter ...

The corresponding GEDCOM Tag is '_DATE' so this field is not formally defined in the GEDCOM 5.5 standard.  The FH Help file does contain the following: You are recommended to provide a Title for all multimedia items. If possible you should also provide a Date - this is the date at which the object w...

Working link:
http://www.fhug.org.uk/wiki/doku.php?id ... iple_names

Hi lossieloon,
I find that I prefer to keep FH's default colour scheme to distinguish diagram-root, ancestors, descendants, and spouses, so I vary the box-shape for certain flags, as well as using icons for other flags. Just a thought.[smile]

Unfortuantely the use of mixed-case surnames often produce ambiguity since so many in my tree have surnames such as Martin, Roy, and James and/or forenames like Richmond, Balfour, Hossack, Scott, and Campbell, which are also used by others as surnames. And despite my best efforts, I do have quite a ...

Brian,
I have a similar issue with various Scottish surnames.  I don't think there is any way to achieve what we need currently (v.4.0.2), so I have added a new Wish-List Request:
http://www.fhug.org.uk/cgi-bin/index.cg ... 85&start=0