Family Historian User Group

Hi Jon, Yes, I'm very familiar with that article; the original questions in it were mine ... back in Nov 2002 [smile] However, the problem was suppose to have been fixed in a much earlier version of FH. I think I may have found a new situation in which the problem occurs. In reply to Jane, I've trie...

Support more than one FH Function in a Query Title. For example: How =Name(['Starting Person']) is related to =Name(['Ending Person']) - nearest 5 Relationships stops after the first =Name() function; 'is related ...... 5 Relationships' does not get printed. =CombineText() does not appear to help in...

I think I have found a bug in FH queries. I have a query that displays the relationship between two specific individuals. In the query, the second =RecordId() reference is producing a duplicate, unecessary, request for parameter entry. See http://www.jamesfamily.vispa.com/recordid.html for a screens...

I'd like to see the ability to specify filter values based on a drop-down list which contains the actual content of a given field. This feature is available for selecting a 'Starting Individual' for a Query (by including a Relationship filter with 'This Individual' selected) but not for other fields...

Very minor wish list suggestion - could the Auto-text heading for the 1841 UK Census to say 'Born in same County' or similar, to match the forms, rather than 'Where Born' which appears in later censuses.

Or have a Option to select whichever you prefer.

Thanks

ID:2866

In addition to the excellent sugestions above, I also have Flags for Will, Probate and Intestate, which I set on the Individual record as appropriate, and display an Icon on Diagrams (along with BMD and Census Icons). This gives a very quick visual record of what's on file as I'm working off the dia...

It would be very helpful, in the Properties Window, to be able to: - see the named Lists a record is in - add/remove records to/from Named Lists, including List Notes - support other functionality previously requested in Wish List items, including the ability to move records between Lists with their...

Excellent; I've voted 5 for it! Perhaps that, mine and this - http://www.fhug.org.uk/cgi-bin/index.cg ... y&num=2742 - should be combined.

I'm game, Chris, though my use has been limited so far.

John

SNAP!  I hit just this problem this morning.  It's a problem with Gedcom, as it defines ASSO as an attribute of INDI, rather than, properly, as a relationship between them (Gedcom is not a database definition). However, as suggested, FH could work around this by always (or at least optionally) inser...

This is another example in support of my Wish List Request (see http://www.fhug.org.uk/cgi-bin/index.cgi?action=forum&board=WishList&op=display&num=2728 ) for the looping index notation to be supported in all situations where multiple occurences of fields and/or records can occur. Without it, the qu...

Monday March 3rd, 9:30pm [tongue]

John James
Dorset, UK

Excellent proposal; for example, I'd like to be able to Flag a Family to show I hold the Marriage/Civil Partnership/Divorce documents (where appropriate) rather than the Individuals.

The Advanced Topics in the online Help are, somewhat oddly, located under 'General Topics' in the online Help. Can they be 'promoted' to a section at the same level in the document hierarchy as 'General Topics'? It would make them rather easier to find and differentiate them from General Topics, whi...

I cant find any reference to 'Query by Event' anywhere? Not sure to what you refer? I had a situation where I had a DEAT event with multiple local NOTEs. Using =GetLabelledText(%.....NOTE2%,['Label']) in an Individual query (there are no Event queries) to locate a given labelled text string only eve...

In that example I'd want the reference to the location of the text returned or null, say. That was but one example. Many other query languages I've worked with in the past are flexible enough to do this. Another way would be to have a wider range of 'primitive' functions that could be combined/embed...

Nick, happy to help if you still want willing vict .... sorry, volunteers.

John

The 'Looping Index' notation should be supported by data references in ALL situations where a field/record can legitimately be repeated in the gedcom file. For example, it is legitimate to have more than one NOTE attached to a DEAT, but %INDI.DEAT.NOTE2[1+] only picks up the first occurence (as does...

Where functions currently expect either text strings OR data references, they should be able to accept text strings, data references or the text strings/data references returned from embedded functions. That would allow far more, and more powerful, expressions to be built. For example, =ContainsText...

Either one function, to return 'Paternal/Maternal/null' or equivalent values to identify whether and which line an ancestor is in relative to an individual

OR

2 specific functions, =PaternalAncestor() and =MaternalAncestor() to do the same.

ID:2680

The ability to specify a list of values, rather than just one single value, against a filter in a Query.

E.g. Add if [field] equals (any of) a,b,c,d, .... etc

ID:2679

It would be nice to be able to define a set of 'global' flags that would be standard across all gedcom files on a computer, as well as 'local' flags that were specific to a particular gedcom (as the current flags are).  The 'global' flags would appear as options in every gedcom on the computer. This...

Aha, I had taken another interpretation suggesting an earlier version of the Wish List, rather than the Wish List Requests list [rolleyes]

What/where is the 'pre wish list'?  I cannot find it, or anything called 'allow data references' on the site via 'Search', so I could be forgiven for not knowing it was already covered.[confused] Nevertheless, I concede that it could be covered by my response to http://www.fhug.org.uk/cgi-bin/index....

FH should provide a complete set of Template Codes to cover every field/attribute; currently there is only a subset. For example, there is no {age}.

ID:2658