Thanks for that, Mike. Your amplification may be found helpful, and encourage our colleagues to adopt fail-safe procedures. After close on 7 years, I have just dealt with the failure of the hard disk. Mercifully my back-up to external drive was made the previous day, there had been some slight warning signs. Nothing has been lost. Martin.

P.S. Correction: The initial Record Window Column 'Expression' needs a leading '=' symbol. i.e. '=TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"GRO:")="","","GRO: ")' -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 15 October 2011 17:15 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Ed, Remember it is a Fact Query so the Row Filters must refer to %FACT% not %INDI% data items. Use Rows Filters such as: Add if =FactName(%FACT%) matches 'To Do' Exclude if =GetLabelledText(%FACT.NOTE2%,["Label"]) is null Regarding your afterthought, no it does not matter how the paragraph is created. However, on re-reading the Function description I realise that I have mislead you. The "Label" does NOT have to start at the beginning of a paragraph, it can appear anywhere, so it does have to be unique. Therefore, ensure each "Label" ends with a colon (:) as you have done, and include the colon (:) in the "Label" parameter, e.g. GRO: Since you are simply looking for a quick way of identifying Individuals with particular 'To Do' entries then you could use the 'Individual Record Window Columns'. To illustrate what I mean, open the Individual 'Records Window' and use 'Lists > Configure Record Window Columns'. Scroll to the bottom of the 'Item' list on the left and select <Other...> then click '>' and enter a 'Heading' such as 'To Do'. Enter an 'Expression' of 'TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"GRO:")="","","GRO: ")' and select 'Default Sort Direction' as 'Descending' and click 'OK' twice. Now all 'Individuals' with a To Do 'GRO:' entry are at the top of the Record Window. To extend this idea for all To Do 'Labels' you could add a separate Column for each 'Label'. However, the following 'Expression' combines them all into one Column. =Text( TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"GRO:")="","","GRO: ") . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"Census:")="","","Census: ") . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"TNA:")="","","TNA: ") ) Just keep adding similar . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"Label:")="","","Label: ") functions for each To Do 'Label'. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Ed Thomas Sent: 15 October 2011 14:11 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Once again, Mike, many thanks for your much appreciated help. I've tried your suggestion of running a fact query and see what you mean. I'm quite attracted to your idea of searching for paragraph headings beginning with specific words or phrase, as opposed to running a query based simply on the note containing the word or phrase. However, try as I might I can't get it to work! Here are the various settings I've used: I've got 5 individuals each with a dummy To Do attribute. (I've configured the To Do tab to show the date, which was your idea, and one large note box, which was Jane's. Thus I'll be entering multiple To Do tasks in the one box, rather than having a new To Do attribute for each task.) Some of the tasks begin with 'GRO:' (followed by a desription of the task itself) and others have random sentences containing one or more words with 'gro' in them - 'growth', etc - but which don't have a paragraph beginning with 'GRO'. I've kept these entries for all the following queries: 1. Individual Query Column: %INDI% Filter: Exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains [parameter] Parameter: gro Result: produced all individuals with 'GRO' at the start of the paragraph and words containing 'gro' in the text (5 individuals). 2. Individual Query Column: %INDI% Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: exactly the same as query 1. 3. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: no records produced. 4. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude unless =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: 6119 families and individuals As mentioned above, I like the idea of the query producing results that are based on the first word of a paragraph. It's just that I can't get it to work. At the end of the day, I'm happy to have the query produce results for To Do tasks that contain, say, GRO and words with 'gro' in them. But now you've brought to my attention the possibility of using a paragraph heading search, it would be nice if I could incorporate that into my query. Thanks again and sorry if I'm becoming a bit of a nuisance!. Regards Ed An afterthought: It might sound like an odd question but does the way the GetLabelledText function work depend on how the paragraph is created? I've entered a note in the To Do attribute that begins "GRO: locate entry for birth.", pressed the enter key twice (thereby leaving a blank line between the two paragraphs) and entered the next 'to do' ("Census: locate in 1871. Possibly living in Basingstoke."). I've also made the same entries but with no blank line between the two tasks (ie, pressed the enter key once). Unsurprisingly, neither way appears to make any difference to the query results. -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 14 October 2011 21:00 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab In your particular case it makes little difference whether you use an Individual Query or a Fact Query, and I don't think you are going against any conventions. I should point out that the =GetRecord(%FACT%) Column gives exactly the same Record as your %INDI% Column i.e. it lists the Record that contains the Fact. Try it and you will see what I mean. I also think that your 2nd & 3rd hidden Columns, and the 1st Exclude if Rows filter, can all be omitted, and still produce the same Result Set. The reason that the two approaches are equivalent is because you only have at most one To Do attribute per Individual and are not listing the To Do Note text itself. The Fact Query comes into its own when you want to list multiple Facts per Individual (such as Census), and also be able to list Facts per Family record. I would advise the use of Row Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null because it only checks the beginning of each Note paragraph. Whereas, Row Filter: Exclude unless %INDI._ATTR-TO_DO.NOTE2% contains ["String"] will search the entire Note and may include Records you don't want. For example if "String" is "GRO" then it will match a Note containing "GRO" or "gro" anywhere. Whereas if "Heading" is "GRO" it will only match if a Note paragraph starts with "GRO" or "gro". However, the risk of such mismatches can be minimised by ticking the 'Match case' option, but then you have to enter the Parameter in the appropriate case to match your heading. Regards, Mike Tate ------------------------------- To unsubscribe from the list, please send an email to FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

Ed, Remember it is a Fact Query so the Row Filters must refer to %FACT% not %INDI% data items. Use Rows Filters such as: Add if =FactName(%FACT%) matches 'To Do' Exclude if =GetLabelledText(%FACT.NOTE2%,["Label"]) is null Regarding your afterthought, no it does not matter how the paragraph is created. However, on re-reading the Function description I realise that I have mislead you. The "Label" does NOT have to start at the beginning of a paragraph, it can appear anywhere, so it does have to be unique. Therefore, ensure each "Label" ends with a colon (:) as you have done, and include the colon (:) in the "Label" parameter, e.g. GRO: Since you are simply looking for a quick way of identifying Individuals with particular 'To Do' entries then you could use the 'Individual Record Window Columns'. To illustrate what I mean, open the Individual 'Records Window' and use 'Lists > Configure Record Window Columns'. Scroll to the bottom of the 'Item' list on the left and select <Other...> then click '>' and enter a 'Heading' such as 'To Do'. Enter an 'Expression' of 'TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"GRO:")="","","GRO: ")' and select 'Default Sort Direction' as 'Descending' and click 'OK' twice. Now all 'Individuals' with a To Do 'GRO:' entry are at the top of the Record Window. To extend this idea for all To Do 'Labels' you could add a separate Column for each 'Label'. However, the following 'Expression' combines them all into one Column. =Text( TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"GRO:")="","","GRO: ") . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"Census:")="","","Census: ") . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"TNA:")="","","TNA: ") ) Just keep adding similar . TextIf(GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,"Label:")="","","Label: ") functions for each To Do 'Label'. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Ed Thomas Sent: 15 October 2011 14:11 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Once again, Mike, many thanks for your much appreciated help. I've tried your suggestion of running a fact query and see what you mean. I'm quite attracted to your idea of searching for paragraph headings beginning with specific words or phrase, as opposed to running a query based simply on the note containing the word or phrase. However, try as I might I can't get it to work! Here are the various settings I've used: I've got 5 individuals each with a dummy To Do attribute. (I've configured the To Do tab to show the date, which was your idea, and one large note box, which was Jane's. Thus I'll be entering multiple To Do tasks in the one box, rather than having a new To Do attribute for each task.) Some of the tasks begin with 'GRO:' (followed by a desription of the task itself) and others have random sentences containing one or more words with 'gro' in them - 'growth', etc - but which don't have a paragraph beginning with 'GRO'. I've kept these entries for all the following queries: 1. Individual Query Column: %INDI% Filter: Exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains [parameter] Parameter: gro Result: produced all individuals with 'GRO' at the start of the paragraph and words containing 'gro' in the text (5 individuals). 2. Individual Query Column: %INDI% Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: exactly the same as query 1. 3. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: no records produced. 4. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude unless =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: 6119 families and individuals As mentioned above, I like the idea of the query producing results that are based on the first word of a paragraph. It's just that I can't get it to work. At the end of the day, I'm happy to have the query produce results for To Do tasks that contain, say, GRO and words with 'gro' in them. But now you've brought to my attention the possibility of using a paragraph heading search, it would be nice if I could incorporate that into my query. Thanks again and sorry if I'm becoming a bit of a nuisance!. Regards Ed An afterthought: It might sound like an odd question but does the way the GetLabelledText function work depend on how the paragraph is created? I've entered a note in the To Do attribute that begins "GRO: locate entry for birth.", pressed the enter key twice (thereby leaving a blank line between the two paragraphs) and entered the next 'to do' ("Census: locate in 1871. Possibly living in Basingstoke."). I've also made the same entries but with no blank line between the two tasks (ie, pressed the enter key once). Unsurprisingly, neither way appears to make any difference to the query results. -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 14 October 2011 21:00 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab In your particular case it makes little difference whether you use an Individual Query or a Fact Query, and I don't think you are going against any conventions. I should point out that the =GetRecord(%FACT%) Column gives exactly the same Record as your %INDI% Column i.e. it lists the Record that contains the Fact. Try it and you will see what I mean. I also think that your 2nd & 3rd hidden Columns, and the 1st Exclude if Rows filter, can all be omitted, and still produce the same Result Set. The reason that the two approaches are equivalent is because you only have at most one To Do attribute per Individual and are not listing the To Do Note text itself. The Fact Query comes into its own when you want to list multiple Facts per Individual (such as Census), and also be able to list Facts per Family record. I would advise the use of Row Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null because it only checks the beginning of each Note paragraph. Whereas, Row Filter: Exclude unless %INDI._ATTR-TO_DO.NOTE2% contains ["String"] will search the entire Note and may include Records you don't want. For example if "String" is "GRO" then it will match a Note containing "GRO" or "gro" anywhere. Whereas if "Heading" is "GRO" it will only match if a Note paragraph starts with "GRO" or "gro". However, the risk of such mismatches can be minimised by ticking the 'Match case' option, but then you have to enter the Parameter in the appropriate case to match your heading. Regards, Mike Tate

Once again, Mike, many thanks for your much appreciated help. I've tried your suggestion of running a fact query and see what you mean. I'm quite attracted to your idea of searching for paragraph headings beginning with specific words or phrase, as opposed to running a query based simply on the note containing the word or phrase. However, try as I might I can't get it to work! Here are the various settings I've used: I've got 5 individuals each with a dummy To Do attribute. (I've configured the To Do tab to show the date, which was your idea, and one large note box, which was Jane's. Thus I'll be entering multiple To Do tasks in the one box, rather than having a new To Do attribute for each task.) Some of the tasks begin with 'GRO:' (followed by a desription of the task itself) and others have random sentences containing one or more words with 'gro' in them - 'growth', etc - but which don't have a paragraph beginning with 'GRO'. I've kept these entries for all the following queries: 1. Individual Query Column: %INDI% Filter: Exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains [parameter] Parameter: gro Result: produced all individuals with 'GRO' at the start of the paragraph and words containing 'gro' in the text (5 individuals). 2. Individual Query Column: %INDI% Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: exactly the same as query 1. 3. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: no records produced. 4. Fact Query Column: =GetRecord(%FACT%) Filter: Exclude unless =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null Parameter/heading: gro Result: 6119 families and individuals As mentioned above, I like the idea of the query producing results that are based on the first word of a paragraph. It's just that I can't get it to work. At the end of the day, I'm happy to have the query produce results for To Do tasks that contain, say, GRO and words with 'gro' in them. But now you've brought to my attention the possibility of using a paragraph heading search, it would be nice if I could incorporate that into my query. Thanks again and sorry if I'm becoming a bit of a nuisance!. Regards Ed An afterthought: It might sound like an odd question but does the way the GetLabelledText function work depend on how the paragraph is created? I've entered a note in the To Do attribute that begins "GRO: locate entry for birth.", pressed the enter key twice (thereby leaving a blank line between the two paragraphs) and entered the next 'to do' ("Census: locate in 1871. Possibly living in Basingstoke."). I've also made the same entries but with no blank line between the two tasks (ie, pressed the enter key once). Unsurprisingly, neither way appears to make any difference to the query results. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 14 October 2011 21:00 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab In your particular case it makes little difference whether you use an Individual Query or a Fact Query, and I don't think you are going against any conventions. I should point out that the =GetRecord(%FACT%) Column gives exactly the same Record as your %INDI% Column i.e. it lists the Record that contains the Fact. Try it and you will see what I mean. I also think that your 2nd & 3rd hidden Columns, and the 1st Exclude if Rows filter, can all be omitted, and still produce the same Result Set. The reason that the two approaches are equivalent is because you only have at most one To Do attribute per Individual and are not listing the To Do Note text itself. The Fact Query comes into its own when you want to list multiple Facts per Individual (such as Census), and also be able to list Facts per Family record. I would advise the use of Row Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null because it only checks the beginning of each Note paragraph. Whereas, Row Filter: Exclude unless %INDI._ATTR-TO_DO.NOTE2% contains ["String"] will search the entire Note and may include Records you don't want. For example if "String" is "GRO" then it will match a Note containing "GRO" or "gro" anywhere. Whereas if "Heading" is "GRO" it will only match if a Note paragraph starts with "GRO" or "gro". However, the risk of such mismatches can be minimised by ticking the 'Match case' option, but then you have to enter the Parameter in the appropriate case to match your heading. Regards, Mike Tate

In your particular case it makes little difference whether you use an Individual Query or a Fact Query, and I don't think you are going against any conventions. I should point out that the =GetRecord(%FACT%) Column gives exactly the same Record as your %INDI% Column i.e. it lists the Record that contains the Fact. Try it and you will see what I mean. I also think that your 2nd & 3rd hidden Columns, and the 1st Exclude if Rows filter, can all be omitted, and still produce the same Result Set. The reason that the two approaches are equivalent is because you only have at most one To Do attribute per Individual and are not listing the To Do Note text itself. The Fact Query comes into its own when you want to list multiple Facts per Individual (such as Census), and also be able to list Facts per Family record. I would advise the use of Row Filter: Exclude if =GetLabelledText(%INDI._ATTR-TO_DO.NOTE2%,["Heading"]) is null because it only checks the beginning of each Note paragraph. Whereas, Row Filter: Exclude unless %INDI._ATTR-TO_DO.NOTE2% contains ["String"] will search the entire Note and may include Records you don't want. For example if "String" is "GRO" then it will match a Note containing "GRO" or "gro" anywhere. Whereas if "Heading" is "GRO" it will only match if a Note paragraph starts with "GRO" or "gro". However, the risk of such mismatches can be minimised by ticking the 'Match case' option, but then you have to enter the Parameter in the appropriate case to match your heading. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Ed Thomas Sent: 14 October 2011 18:52 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Thanks Mike. I've approached the query from the point of view of the individual rather than the fact because I want to see which individuals have outstanding research to do, rather than see what outstanding work I've got to do(if that makes sense). I've got the query set up as an individual query using the following settings: 3 Columns: %INDI%, %INDI._ATTR-TO_DO[1]% and %INDI._ATTR-TO_DO[1].NOTE2[1]% (the attribute and the note are hidden, the individual is sorted in ascending order). 2 Rows: Exclude if %INDI._ATTR-TO_DO[1].NOTE2[1]% is null, and exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains "" The results provide me with what I want, namely a list of individuals with items of research to do. I'm not too bothered about seeing the full note in the results as I can double click on the individual's name to bring up the property dialogue box. I'm more than willing to admit that the query may go against convention (I don't know, does it? - and if so, does it matter so long as it gives me what I want?). What are the advantages of running the query as a fact rather than individual query? Thanks for your helpful suggestions and insights, they're much appreciated. Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 14 October 2011 12:33 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Ed, One snag with your Rows Filter idea is that if any To Do Note has both say "GRO" and "Census" notes then both Notes will be included when the Parameter is either "GRO" or "Census". (BTW the Filter actually needs to use %FACT.NOTE2% not %INDI._ATTR-TO_DO[1].NOTE2[1]% because it is Fact Query not an Individual Query.) You can be even more selective by using the =GetLabelledText() function - see FH Help for details. Use a Column such as Note =GetLabelledText(%FACT.NOTE2%,["Heading"]) instead of the multiple Note columns Use a Rows Filter such as Exclude if =GetLabelledText(%FACT.NOTE2%,["Heading"]) is null. Then only paragraphs starting with the "Heading" parameter are included in the Result Set. Regards, Mike Tate

Thanks Mike. I've approached the query from the point of view of the individual rather than the fact because I want to see which individuals have outstanding research to do, rather than see what outstanding work I've got to do(if that makes sense). I've got the query set up as an individual query using the following settings: 3 Columns: %INDI%, %INDI._ATTR-TO_DO[1]% and %INDI._ATTR-TO_DO[1].NOTE2[1]% (the attribute and the note are hidden, the individual is sorted in ascending order). 2 Rows: Exclude if %INDI._ATTR-TO_DO[1].NOTE2[1]% is null, and exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains "" The results provide me with what I want, namely a list of individuals with items of research to do. I'm not too bothered about seeing the full note in the results as I can double click on the individual's name to bring up the property dialogue box. I'm more than willing to admit that the query may go against convention (I don't know, does it? - and if so, does it matter so long as it gives me what I want?). What are the advantages of running the query as a fact rather than individual query? Thanks for your helpful suggestions and insights, they're much appreciated. Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 14 October 2011 12:33 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Ed, One snag with your Rows Filter idea is that if any To Do Note has both say "GRO" and "Census" notes then both Notes will be included when the Parameter is either "GRO" or "Census". (BTW the Filter actually needs to use %FACT.NOTE2% not %INDI._ATTR-TO_DO[1].NOTE2[1]% because it is Fact Query not an Individual Query.) You can be even more selective by using the =GetLabelledText() function - see FH Help for details. Use a Column such as Note =GetLabelledText(%FACT.NOTE2%,["Heading"]) instead of the multiple Note columns Use a Rows Filter such as Exclude if =GetLabelledText(%FACT.NOTE2%,["Heading"]) is null. Then only paragraphs starting with the "Heading" parameter are included in the Result Set. Regards, Mike Tate

Ed, One snag with your Rows Filter idea is that if any To Do Note has both say "GRO" and "Census" notes then both Notes will be included when the Parameter is either "GRO" or "Census". (BTW the Filter actually needs to use %FACT.NOTE2% not %INDI._ATTR-TO_DO[1].NOTE2[1]% because it is Fact Query not an Individual Query.) You can be even more selective by using the =GetLabelledText() function - see FH Help for details. Use a Column such as Note =GetLabelledText(%FACT.NOTE2%,["Heading"]) instead of the multiple Note columns Use a Rows Filter such as Exclude if =GetLabelledText(%FACT.NOTE2%,["Heading"]) is null. Then only paragraphs starting with the "Heading" parameter are included in the Result Set. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Ed Thomas Sent: 13 October 2011 18:47 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab Thanks Mike. The addition of the date box is a nice touch! Beginning each new To Do item in the notes box with a simple 'heading' (eg GRO, Census, TNA, Baptism, Obituary, etc or whatever is meaningful/pertinent for you) also allows you to refine a custom query by adding a parameter for the note box (eg exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains parameter (say, GRO). Regards Ed -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 13 October 2011 16:11 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab You could add the field INDI._ATTR-TO_DO[1].DATE to your To Do tab and then won't need to go to the new Attribute to enter the date. This technique also allows you to produce a complete To Do list Query Report. Use a Query Type of Fact Set Columns such as: Owner =GetRecord(%FACT%) Note 1 =GetParagraph(%FACT.NOTE2%,1) Note 2 =GetParagraph(%FACT.NOTE2%,2) Note 3 =GetParagraph(%FACT.NOTE2%,3) Set Rows Filter: Add if =FactName(%FACT%) matches 'To Do' The multiple Note columns are needed to display all the Note otherwise you only get the first line followed by ellipsis (...) You could probably also produce a To Do Report by using the Report Options to only include To Do attributes in a Custom Report. Regards, Mike Tate

Thanks Mike. The addition of the date box is a nice touch! Beginning each new To Do item in the notes box with a simple 'heading' (eg GRO, Census, TNA, Baptism, Obituary, etc or whatever is meaningful/pertinent for you) also allows you to refine a custom query by adding a parameter for the note box (eg exclude unless %INDI._ATTR-TO_DO[1].NOTE2[1]% contains parameter (say, GRO). Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 13 October 2011 16:11 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Property Box Custom Tab You could add the field INDI._ATTR-TO_DO[1].DATE to your To Do tab and then won't need to go to the new Attribute to enter the date. This technique also allows you to produce a complete To Do list Query Report. Use a Query Type of Fact Set Columns such as: Owner =GetRecord(%FACT%) Note 1 =GetParagraph(%FACT.NOTE2%,1) Note 2 =GetParagraph(%FACT.NOTE2%,2) Note 3 =GetParagraph(%FACT.NOTE2%,3) Set Rows Filter: Add if =FactName(%FACT%) matches 'To Do' The multiple Note columns are needed to display all the Note otherwise you only get the first line followed by ellipsis (...) You could probably also produce a To Do Report by using the Report Options to only include To Do attributes in a Custom Report. Regards, Mike Tate ------------------------------- To unsubscribe from the list, please send an email to FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

<<snippet>> You can enter a note directly into the note box as it appears on the To Do tab. This will automatically create a new To Do attribute without you having to manually select it. However, you will have to go to the new attribute and enter a date of 0000 for it to appear at the top of the list of facts. <<snippet>> You could add the field INDI._ATTR-TO_DO[1].DATE to your To Do tab and then won't need to go to the new Attribute to enter the date. This technique also allows you to produce a complete To Do list Query Report. Use a Query Type of Fact Set Columns such as: Owner =GetRecord(%FACT%) Note 1 =GetParagraph(%FACT.NOTE2%,1) Note 2 =GetParagraph(%FACT.NOTE2%,2) Note 3 =GetParagraph(%FACT.NOTE2%,3) Set Rows Filter: Add if =FactName(%FACT%) matches 'To Do' The multiple Note columns are needed to display all the Note otherwise you only get the first line followed by ellipsis (...) You could probably also produce a To Do Report by using the Report Options to only include To Do attributes in a Custom Report. Regards, Mike Tate

Dear Jane   Thank you very much.  Your solution achieved what I needed.   Regards  Anita

Dear Jane   You only appear to have received half of my e-mail, so I am forwarding it again.  Thank you for your reply already received and I will try your solution.   Anita Davey ----- Forwarded Message ----- From: Anita Davey <anitadavey@ymail.com> To: "family-historian-users@rootsweb.com" <family-historian-users@rootsweb.com> Sent: Thursday, 13 October 2011, 15:20 Subject: Printing Reports from The Records Window Listing or Query Result Set Dear FHUG I am trying to print an "All Individuals" Report using either The Records Window Listing or Query Window. The problem I am having is that I cannot get it to put the Surname first in either report type. The Query Window, particularly, will not allow me to set up data using the > symbol -the symbol does not become available when I have highlighted  SURNAME FIRST from the data list. Can anyone help, please? Anita Davey

I've now had a play around with Jane's idea and am very pleased with the results. For the benefit of others who may be interested in adapting this for their own requirements here's what I'll use it for and how I've got it configured (apologies for the length): Essentially the new custom tab is a 'To Do' list for individuals. I've never really liked the idea of using a named list for itemising work in progress (a To Do list). I much prefer the idea of having such notes 'attached' to the individual's properties/details rather than having them appear in a 'separate' feature. That's just my personal preferance. However, as mentioned in my original post, I've never been quite able to set up such a feature. I've known what I wanted but not been able to get it (not even sure if it was possible). Following Jane's advice, I created a custom attribute, called it 'To Do' and gave it the imaginative label 'To Do'. It appears that, when creating custom events/attributes, you have to provide a template (for narrative reports), so I added any old template (in this case {abbr}). It doesn't matter to me what template I use as it won't appear in any individual or family reports (more of which later). Next I created a custom tab and called it 'To Do'. The only item that I've selected to appear in the new tab are the notes from the newly-created 'To Do' attribute. I've configured the 'To Do' item thus: Custom Item Name: To Do Part 1 ticked Label: blank (I entered a space using the space bar, as entering something is mandatory - I didn't particularly want anything to appear at the side of or above the item in the tab, hence the blank space). Data Reference: INDI._ATTR-TO_DO[1].NOTE2[1] Variable Height: ticked To enter notes, details of things to do, etc that relate specifically to the selected individual, enter a fact in the usual way, selecting, of course, the newly-created 'To Do' attribute. In the note section enter whatever's relevant to your requirements - this is what will appear in the 'To Do' tab. Next, I experimented with where I wanted the new attribute to appear in the list of facts (which, like most people, I have sorted in date order). Where it appears depends on what is entered in the date box. If it's left blank, it will appear just before the person's death (if you have recorded one). If you enter something like 2075 (to force it to appear after all the recorded facts), it just looks a little odd and will appear at the bottom of the list of facts, which could be out of sight, depending on how many facts you have recorded for an individual. I settled on using the equally odd but much more pragmatic date of 0000. This forces the To Do attribute to appear at the top of the list of facts, above the birth event. Thus no matter how many facts are recorded, the To Do attribute always appears at the top of the pile and is immediately visible whenever the Facts tab of the property dialogue box is opened. I intend to have just one 'To Do' attribute for each individual (but only if one's required). In the note box of the attribute I anticipate beginning each new note entry with the date of writing (eg, 13/10/2011) followed by a description of what's required. Each new entry will start on a new line - possibly separated from the last entry by a space, just to make it easier to read (I haven't decided yet, but it's not important from the point of view of how the setup actually works). I don't see any reason for having a separate To Do attribute for each and every item of work in progress/things to do. That would just bloat the facts list and clutter it up. However, there's nothing to stop you from doing that if that's what you want. You'll just have to remember to add a new custom To Do notes item in the To Do tab, with each one given a corresponding data reference (INDI._ATTR-TO_DO[1], INDI._ATTR-TO_DO[2], INDI._ATTR-TO_DO[3], etc). Again, this could lead to a cluttered/bloated appearance. I think one attribute and one large notes box looks better and is easier to use. You can enter a note directly into the note box as it appears on the To Do tab. This will automatically create a new To Do attribute without you having to manually select it. However, you will have to go to the new attribute and enter a date of 0000 for it to appear at the top of the list of facts. To ensure the 'To Do' attibute does not appear in standard reports (individuals, family group sheets, etc) you need to configute the report options. In the report window, click on the 'Options' button on the right. On the Contents tab, under 'Individual Events/ Attributes', select 'Exclude List' and then click on the 'Edit List' button. From the list of attributes, select the 'To Do' attribute, send it to the list box on the right and click ok. This will exclude the To Do attribute from appearing in any future reports. All this may seem seem a bit long winded and perhaps even cumbersome. But it works for me and I thought other users would find it interesting - even if it's not really for them. Thanks to Jane for her creative suggestion and Simon for developing such a flexible and configurable program. Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? What not create a custom attribute for Additional Notes, you can add notes to attributes and easily exclude specific attributes from reports and build custom reports only containing a single attribute for example. Then you can build your custom tab with the Note for the Additional Note Attribute and using the variable height option to get a "big" note box. On 12 October 2011 15:04, Ed Thomas <cavasta@yahoo.co.uk> wrote: > give them the heading 'additional notes' -- Jane.

I am not quite sure what you want to do, but on a query just save the standard All Individuals Query as a custom one using the menu button on the right at the top. Then you will be able to edit your new custom query to add the new column. On 13 October 2011 14:20, Anita Davey <anitadavey@ymail.com> wrote: > The Query Window, particularly, will not allow me to set up data using the > symbol -the symbol does not become available when I have highlighted  SURNAME FIRST from the data list. -- Jane. Jane Taubman | www.rjt.org.uk | www.taubman.org.uk |www.fhug.org.uk

Dear FHUG   I am trying to print an "All Individuals" Report using either The Records Window Listing or Query Window.   The problem I am having is that I cannot get it to put the Surname first in either report type.   The Query Window, particularly, will not allow me to set up data using the > symbol -the symbol does not become available when I have highlighted  SURNAME FIRST from the data list.   Can anyone help, please?   Anita Davey

Interesting solution/idea. I'll have a play around. Thanks Jane Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...? ------------------------------- What not create a custom attribute for Additional Notes, you can add notes to attributes and easily exclude specific attributes from reports and build custom reports only containing a single attribute for example. Then you can build your custom tab with the Note for the Additional Note Attribute and using the variable height option to get a "big" note box. On 12 October 2011 15:04, Ed Thomas <cavasta@yahoo.co.uk> wrote: > give them the heading 'additional notes' -- Jane. Jane Taubman | www.rjt.org.uk | www.taubman.org.uk |www.fhug.org.uk ------------------------------- To unsubscribe from the list, please send an email to FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

What not create a custom attribute for Additional Notes, you can add notes to attributes and easily exclude specific attributes from reports and build custom reports only containing a single attribute for example. Then you can build your custom tab with the Note for the Additional Note Attribute and using the variable height option to get a "big" note box. On 12 October 2011 15:04, Ed Thomas <cavasta@yahoo.co.uk> wrote: > give them the heading 'additional notes' -- Jane. Jane Taubman | www.rjt.org.uk | www.taubman.org.uk |www.fhug.org.uk

I know I can add a custom tab to the property dialogue box. Is there any way I can add a custom tab and call it something like 'additional notes', the layout and properties of which would be similar to the notes tab that comes as a standard feature? I want the custom notes tab to allow me to add notes that are separate from and different to the standard notes; I don't want the additional notes to appear in the standard notes tab. I've been able to add a custom tab and populate it with a notes box. However, the way I've been doing this means that the notes that appear are the same ones as those that appear in the notes tab. I suspect there isn't a way of doing this but I thought I'd ask anyway. The only way round that I've found would be to add notes in the standard notes tab, give them the heading 'additional notes' (or whatever's appropriate) and make them private (as I wouldn't want them to appear in reports). Alternatively, I suppose I could also use a named list. Regards Ed ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ What would George Smiley do...?

For a detailed tutorial on the capabilities of Diagram Text Scheme editing see the book "Getting the Most From Family Historian 4" PDF on the FH Help menu. "Chapter 9 - Setting the Style, Layout & Content of Diagrams" is particularly pertinent. If you prefer you could print these 16 pages to make it easier to follow, while using FH. Also on each of the FH Diagram Options tabs the Help button gives associated advice. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Martin Allen Sent: 12 October 2011 11:06 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Diagram Thanks, both Jane and Mike. I still find things like this that I need to be talked through.

Thanks, both Jane and Mike. I still find things like this that I need to be talked through.

If you also want to inhibit Birth, Marriage, and Death details then edit each of those text scheme items and tick Flag Condition, select Record Flag: Living, and must be not set. -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Jane Taubman Sent: 12 October 2011 10:32 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Diagram Assuming you have set the Living Flag for living people. Change the Name line on your text scheme to check for the living flag: e.g. =TextIf(Exists(%INDI._FLGS.__LIVING%),"Living",%INDI.NAME:GIVEN_ALL%) %INDI.NAME:SURNAME% On 12 October 2011 09:48, Martin Allen <martin.allen17@btinternet.com> wrote: > > Sorry if this is obvious. Is it possible to create a diagram with the most > recent people only shown as 'Living Smith' or equivalent? -- Jane. Jane Taubman | www.rjt.org.uk | www.taubman.org.uk |www.fhug.org.uk ------------------------------- To unsubscribe from the list, please send an email to FAMILY-HISTORIAN-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message