* View Standard & Custom Queries

[jsphillips]

Hi
There does not appear to be any discussions on Queries, Standard or Custom although I could be wrong !
Will there be one version for all persons using versions up to and including 6.27 and another for Version 7 ?
Or will there be one new version updated for all versions, or even all existing Queries to work will work ?

[ColeValleyGirl]

FH7 comes with the usual set of Standard queries and some new ones.

Custom queries may or may not work -- some data references have changed, From the Help File (Notes for Upgraders):

If you previously created or imported any custom queries, it is possible, though unlikely, that these could be affected by some of the data storage changes in version 7, and could, as a result, contain invalid row filters or invalid column specifications. If that happens, the relevant row filters or column specifications will be automatically disabled, and a message will be displayed when you run any such query, that says: "This query contains one or more disabled columns or row filters. Continue anyway?". If you look on the Rows or Columns tabs, you should be able to spot the disabled lines quite easily, in the row filter or column listings, as the text will be greyed, to show that these lines are disabled. In each case, you can either correct the errors and press the Update button, to update and re-enable the line. Or you can delete the erroneous line. If you previously marked the query as 'Read Only'(by ticking 'Read Only' on the General tab), you will need to untick that option before you can make changes to the query.

This issue does not affect standard queries. It only affects custom queries.

[jsphillips]

Thanks will try them all Standard & Custom Queries

[tatewise]

The Standard Queries installed with FH will be compatible with the FH version installed, as has always been the case.

Most Custom Queries will work with both FH v6.2.7 and FH v7.0 but there will be a few exceptions and again that has applied in previous major FH upgrades.

However, any of your Custom Queries from FH v6.2.7 that are imported into FH v7.0 that may need adjusting only need editing once. You won't be switching back and forth between FH v6.2.7 and FH V7.0.

Published downloads from the FHUG KB will need to say which FH version they work with and again that has always been the case if you review the current downloads.

[Gowermick]

Still on the subject of FH7 queries, is there anyway to ‘promote’ an existing query, so that it appears as a choice, immediately one clicks the query buttom, rather than having to drill down to it?

I am thinking along the lines of the property box, where you can specify which regularly used facts appear when you click ‘new fact’.

[ColeValleyGirl]

What I've done is Add the ones I use regularly to a group called 1, which floats to the two of the list, and means I can get there in 2 clicks.

[tatewise]

See the Help page Query Window: General Tab where it explains about Group 1/2/3 and adding new groups & subgroups.

[Gowermick]

Helen & Mike
Thanks for pointing me to right place.

Helen, name the Group _1 and it floats to top, why settle for second place?
My Bad, You meant top of the list, but 2nd in the menu

[E Wilcock]

Jane began her Gedmatch query with ^ so it came top in the sort order .

In Version 6, one clicked the Query icon and Jane's query opened and the blue arrow ran it straight away. Now it does not. Queries are subdivided which means an extra key stroke each time.
I thought I could alter that by moving Jane's query into the top level of the application data query folder. But that doesnt seem to work.
One selects the Query window and then has to select the Query window a second time. In computing terms that doesnt make sense to me.
Can any of the experts please suggest how I can revert the Query display to the behaviour in version 6?

I realise Version 7 has DNA tools but have three times read the DNA tools instructions for version 7. They appear to deal with every blood relative of a selected individual and include DNA matches from ancestry whose place in the tree is actually known.

So for the time being I prefer to stick with Jane's system which relies on Gedmatch fact and a query.