Re Jon's query, for what it's worth, as a lay PC user and not a software
programmer (admit in years past I did a bit of fortran and basic programming
as part of my education), I have no problem with 'Add if/Add unless/Exclude
if/Exclude unless' concepts. They seem clear enough to me and I find I can
accomplish pretty much all the queries I want. I can't comment on whether
the resulting query is the most efficient code but the results satisfy me.
----- Original Message -----
From: "Jon Axtell" <familytree(a)jonaxtell.me.uk>
Sent: Thursday, January 25, 2007 1:49 PM
Subject: Re: [FHU] FAMILY-HISTORIAN-USERS Digest, Vol 2, Issue 46
>Date: Thu, 25 Jan 2007 10:57:31 -0000
>From: "Alan E. White" <family.historian(a)aewhite.me.uk>
> >> Seems Family Historian Queries are for software programmers
> >> and database managers and not for ordinary users.
> >Well, I am - or rather was for twenty years until very recently - both
> >those. And I can't get to grips with FH's query language. So it's
> >you :-)
> >Personally I'd prefer a SQL interface but that's not likely to help many
I too am a software engineer and I have great difficulty understanding the
concept of . It comes across to me as using double negative concepts which
I was brought up to avoid like the plague. I wonder if it really is simple
for non-software people to understand? - maybe us software people have
trouble with it because of our training, whilst it's an easy concept for
non-IT literate people? A question for everybody else.
I would prefer a nice simple AND/OR/NOT query system. Plus a system which
allows grouping of expressions to allow building up complicated queries.
The current system is very simplistic. The current system's concept of add
into list, then remove, then add, then remove depending on which sets of
conditions is being used in a query can be nice and simple and fast, but
is also highly restrictive. Considering the speed of most PCs I wouldn't
mind a slower query system that allowed more flexibility. Even allowing
mixing of family and individuals.
>One of the difficulties seem to be the highly-structured nature of the
>model, which is reflected in the available query selections. This
>rows based on their parent (as in parent record, not parent the person)
>so prevents queries such as:
>"Show me all individuals where one or more of their events or attributes
>a Where Within Source starting RG11/3643, and display the individual and
>line for each of the candidate events."
>Unless anyone can tell me how?
Sorry! :-) The best I can think of is to select every event/attribute and
add them all to the query selecting the where within of all the
events/attributes and matching against your RG11 text. Very very long
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.10/651 - Release Date: