AS modifies the Gedcom so FH has to reload which will close the diagram etc down. There is no way around this and as far as I know there won't be unless FH takes on real time databases but then the compatibility with Gedcom would likely be compromised. It's not dynamic but you could save the diagram as a pdf and open that in Acrobat which wouldn't close ( but wouldn't update either...) -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Beryl & Mike Tate Sent: 10 February 2012 20:07 To: family-historian-users@rootsweb.com Subject: Re: [FHU] Saving from Ancestral Sources I am afraid there seems to be no way to keep the diagram open. -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of JulieandMalcolm@kett.fsnet.co.uk Sent: 10 February 2012 19:47 To: Family Historian Subject: [FHU] Saving from Ancestral Sources Hi, I like to have a diagram open when I’m working on a particular family. When I add census records via Ancestral Sources, and then FH is modified – is there anyway of keeping the diagram open on the screen instead of losing it every time? After saving, it goes back to the Individual Records screen and its a bit tiresome to have to keep re-opening the diagram. I’m using FH Version 4.1.3 and AS version 2.0.0 Many thanks Julie ------------------------------- 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

I am afraid there seems to be no way to keep the diagram open. -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of JulieandMalcolm@kett.fsnet.co.uk Sent: 10 February 2012 19:47 To: Family Historian Subject: [FHU] Saving from Ancestral Sources Hi, I like to have a diagram open when I’m working on a particular family. When I add census records via Ancestral Sources, and then FH is modified – is there anyway of keeping the diagram open on the screen instead of losing it every time? After saving, it goes back to the Individual Records screen and its a bit tiresome to have to keep re-opening the diagram. I’m using FH Version 4.1.3 and AS version 2.0.0 Many thanks Julie

Hi, I like to have a diagram open when I’m working on a particular family. When I add census records via Ancestral Sources, and then FH is modified – is there anyway of keeping the diagram open on the screen instead of losing it every time? After saving, it goes back to the Individual Records screen and its a bit tiresome to have to keep re-opening the diagram. I’m using FH Version 4.1.3 and AS version 2.0.0 Many thanks Julie

Hi all ... myself (Sydney) and uncle (UK) want to start investigating the same family roots! Can we both work off and input to, the same data? Where would this be stored? Do we need to purchase a set of software EACH? Can 'joint' projects WORK? Thanks Graham

On 10 February 2012 03:58, Graham Deverill <graham@deverill.com.au> wrote: > Can we both work off and input to, the same data? > Sort of, what I would recommend is what I do with my Sister, I have used Dropbox to share my Project with her. This means we both have Dropbox installed and the Project folder automatically syncs between us. One limitation of this is you can't both work on the Project at the same time, but if you are working with some one in Australia this may not be much of a problem. Where would this be stored? > Using dropbox the project would be stored on both computers and on the dropbox servers. Do we need to purchase a set of software EACH? Yes. Can 'joint' projects WORK? Good question. My sister does not do much active research, but we get on fine and she adds information when she needs to and we don't often cause a "clash" by both saving at the same time, if it does happen I merge the clash back into the main project. The other option is to use the Merge options to merge separate projects on a regular basis rather than having one single project. -- Jane. Jane Taubman | www.rjt.org.uk | www.taubman.org.uk |www.fhug.org.uk

Thank you. I had 16 instances spread over 3 projects - all Birth records. With the downloaded query, it was so easy to locate and delete them. Your help much appreciated. Patricia -----Original Message----- From: Simon Orde Sent: Wednesday, February 08, 2012 11:29 PM To: FHU Mailing List Subject: [FHU] *** Duplicated 'Cause' Bug Simon Orde List Administrator & Family Historian designer ------------------------------- 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

I thought 'this won't apply to me' but downloaded the query anyway. My composite file of 1400 individuals had one instance! An occupation with a cause of Phthisis (TB) 2 years, obviously copied from the death cause. Thanks for highlighting this.

I would recommend that when completing any boxes in spreadsheets, databases, web forms etc that you always tab out of the box to lock the entered data before moving from the screen. Regards Robin Dew Sent from my iPhone On 8 Feb 2012, at 14:10, Andrea Kent <andrea.kent@btopenworld.com> wrote: > I have just run the 'non death facts with causes' query and am puzzled by the results, I am not sure they relate to exactly the same bug as reported by Simon. I have 3 instances of this superfluous cause, each relating to a custom event. > > The first 'Witness' (e.g. witness at a marriage) has part of the Note duplicated in the Cause (but not exactly the same phrase??) > Note: at the marriage of his daughter Rose to Edward > Cause: Witness at marriage of daughter Rose > > The other 2 are for 'Informant' events (e.g. informants of the death), but in both of these, the Note is empty (although I am sure I entered text in them, and this extra text is now in the Clause). > > Cause: Informant at death of father William > > The sentence of Informant is as follows:{individual} was the {label} {date} {place} <{note}> > so that when the Note is blank, the sentence just reads "He was the informant on 24 Jan 1918 in Oxford", so I don't understand where the Cause is getting the (correct) information of 'at death of father William' from (though again I am sure I originally entered this in the Note. > > Any ideas welcome - meanwhile I will be checking all my other witness and informant facts! > > > Regards, > Andrea > > > ________________________________ > From: Simon Orde <simon-fhu@family-historian.co.uk> > To: FHU Mailing List <FAMILY-HISTORIAN-USERS-L@rootsweb.com> > Sent: Wednesday, 8 February 2012, 10:29 > Subject: [FHU] *** Duplicated 'Cause' Bug > > We have just discovered a bug that is present in the current version (4.1) > of Family Historian (thank you to Roger and Graham for pointing this out). > The bug is associated with the "Cause" box on the Facts tab of the Property > Box. Ordinarily you won't see a Cause box in the Facts tab. It only > appears if you select certain types of event - e.g. death. The symptom of > the bug is that in certain circumstances, the value of the Cause box can be > copied (i.e. duplicated) to other events which don't usually have a cause > associated with them - such as birth or burial. > > The bug happens, and *only* happens, if the cursor is in the Cause Box of > the Facts tab of the Property Box, when you do certain things. For example, > if at this point you click on the 'Go Back', 'Go Foward' or 'Up' buttons on > the Property Box toolbar, the value in the Cause field will be copied to the > first event of the record you navigate to, *if* that event is an event like > Birth which can have a cause, but doesn't usually have one, and which > doesn't get a Cause box in the Facts tab. If the first event is an event > like Death which does get a Cause box in the Facts tab, the bug does not > occur. > > If you think you might have been affected, you can download a query from the > FHUG downloads area (www.fhug.org.uk) called "Non_Death_Facts_With_Causes". > This lists all recorded causes for all events except death events (death > causes won't ever have an invalid value). Don't assume that because a Cause > for an event is listed, it is necessarily a wrong value. It may be a valid > cause (e.g. a divorce or retirement cause). But if you see any cause values > that look wrong, you can easily delete them by clicking on the cell in the > 'Cause' column and pressing the Delete key - and then confirm if asked if > you want to delete the field in question. As always, take backups to be > safe, before doing anything you might regret. > > We apologise for any inconvenience caused. The bug will be fixed in version > 5. Meanwhile, you can prevent this bug happening by not leaving the cursor > in the Cause box of the Facts tab of the Property Box when you click on > toolbar buttons or menu commands. > > Simon Orde > List Administrator & Family Historian designer > > > ------------------------------- > 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 > > ------------------------------- > 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

Hi Andrea, I, too, ran the query out of curiosity, and found two Non-death Custom Facts with causes, in this case related to a military badge award. Looks like I had used 'Cause' to document the reason for the award; 'GC (Good Conduct)' and 'GC&B (Good Conduct and Behaviour)' respectively. Although I'd clearly set it up that way on purpose (the associated sentence also uses the '{cause}' fact variable), I had forgotten I'd done so, as it is some time since I have looked at any badge-holding military ancestors (yes, I use the 'a' word, for my own Grandfather in this case.) I wonder if you've done something similar? John _____ From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Andrea Kent Sent: Wednesday, February 08, 2012 2:10 PM To: family-historian-users@rootsweb.com; FHU Mailing List Subject: Re: [FHU] *** Duplicated 'Cause' Bug I have just run the 'non death facts with causes' query and am puzzled by the results, I am not sure they relate to exactly the same bug as reported by Simon. I have 3 instances of this superfluous cause, each relating to a custom event. The first 'Witness' (e.g. witness at a marriage) has part of the Note duplicated in the Cause (but not exactly the same phrase??) Note: at the marriage of his daughter Rose to Edward Cause: Witness at marriage of daughter Rose The other 2 are for 'Informant' events (e.g. informants of the death), but in both of these, the Note is empty (although I am sure I entered text in them, and this extra text is now in the Clause). Cause: Informant at death of father William The sentence of Informant is as follows:{individual} was the {label} {date} {place} <{note}> so that when the Note is blank, the sentence just reads "He was the informant on 24 Jan 1918 in Oxford", so I don't understand where the Cause is getting the (correct) information of 'at death of father William' from (though again I am sure I originally entered this in the Note. Any ideas welcome - meanwhile I will be checking all my other witness and informant facts! Regards, Andrea ________________________________ From: Simon Orde <simon-fhu@family-historian.co.uk> To: FHU Mailing List <FAMILY-HISTORIAN-USERS-L@rootsweb.com> Sent: Wednesday, 8 February 2012, 10:29 Subject: [FHU] *** Duplicated 'Cause' Bug We have just discovered a bug that is present in the current version (4.1) of Family Historian (thank you to Roger and Graham for pointing this out). The bug is associated with the "Cause" box on the Facts tab of the Property Box. Ordinarily you won't see a Cause box in the Facts tab. It only appears if you select certain types of event - e.g. death. The symptom of the bug is that in certain circumstances, the value of the Cause box can be copied (i.e. duplicated) to other events which don't usually have a cause associated with them - such as birth or burial. The bug happens, and *only* happens, if the cursor is in the Cause Box of the Facts tab of the Property Box, when you do certain things. For example, if at this point you click on the 'Go Back', 'Go Foward' or 'Up' buttons on the Property Box toolbar, the value in the Cause field will be copied to the first event of the record you navigate to, *if* that event is an event like Birth which can have a cause, but doesn't usually have one, and which doesn't get a Cause box in the Facts tab. If the first event is an event like Death which does get a Cause box in the Facts tab, the bug does not occur. If you think you might have been affected, you can download a query from the FHUG downloads area (www.fhug.org.uk) called "Non_Death_Facts_With_Causes". This lists all recorded causes for all events except death events (death causes won't ever have an invalid value). Don't assume that because a Cause for an event is listed, it is necessarily a wrong value. It may be a valid cause (e.g. a divorce or retirement cause). But if you see any cause values that look wrong, you can easily delete them by clicking on the cell in the 'Cause' column and pressing the Delete key - and then confirm if asked if you want to delete the field in question. As always, take backups to be safe, before doing anything you might regret. We apologise for any inconvenience caused. The bug will be fixed in version 5. Meanwhile, you can prevent this bug happening by not leaving the cursor in the Cause box of the Facts tab of the Property Box when you click on toolbar buttons or menu commands. Simon Orde List Administrator & Family Historian designer ------------------------------- 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 ------------------------------- 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 _____ avast! <http://www.avast.com> Antivirus: Inbound message clean. Virus Database (VPS): 07/02/2012 Tested on: 08/02/2012 15:18:03 avast! - copyright (c) 1988-2012 AVAST Software. _____ avast! Antivirus <http://www.avast.com> : Outbound message clean. Virus Database (VPS): 08/02/2012 Tested on: 08/02/2012 15:51:50 avast! - copyright (c) 1988-2012 AVAST Software.

Many thanks Simon. I'm amazed and impressed that you found the problem so quickly!! Best regards Roger Mitchell rdm@mfo.me.uk http://mfo.me.uk -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Simon Orde Sent: 08 February 2012 10:29 To: FHU Mailing List Subject: [FHU] *** Duplicated 'Cause' Bug We have just discovered a bug that is present in the current version (4.1) of Family Historian (thank you to Roger and Graham for pointing this out). The bug is associated with the "Cause" box on the Facts tab of the Property Box. Ordinarily you won't see a Cause box in the Facts tab. It only appears if you select certain types of event - e.g. death. The symptom of the bug is that in certain circumstances, the value of the Cause box can be copied (i.e. duplicated) to other events which don't usually have a cause associated with them - such as birth or burial. The bug happens, and *only* happens, if the cursor is in the Cause Box of the Facts tab of the Property Box, when you do certain things. For example, if at this point you click on the 'Go Back', 'Go Foward' or 'Up' buttons on the Property Box toolbar, the value in the Cause field will be copied to the first event of the record you navigate to, *if* that event is an event like Birth which can have a cause, but doesn't usually have one, and which doesn't get a Cause box in the Facts tab. If the first event is an event like Death which does get a Cause box in the Facts tab, the bug does not occur. If you think you might have been affected, you can download a query from the FHUG downloads area (www.fhug.org.uk) called "Non_Death_Facts_With_Causes". This lists all recorded causes for all events except death events (death causes won't ever have an invalid value). Don't assume that because a Cause for an event is listed, it is necessarily a wrong value. It may be a valid cause (e.g. a divorce or retirement cause). But if you see any cause values that look wrong, you can easily delete them by clicking on the cell in the 'Cause' column and pressing the Delete key - and then confirm if asked if you want to delete the field in question. As always, take backups to be safe, before doing anything you might regret. We apologise for any inconvenience caused. The bug will be fixed in version 5. Meanwhile, you can prevent this bug happening by not leaving the cursor in the Cause box of the Facts tab of the Property Box when you click on toolbar buttons or menu commands. Simon Orde List Administrator & Family Historian designer ------------------------------- 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

I have just run the 'non death facts with causes' query and am puzzled by the results, I am not sure they relate to exactly the same bug as reported by Simon. I have 3 instances of this superfluous cause, each relating to a custom event. The first 'Witness' (e.g. witness at a marriage) has part of the Note duplicated in the Cause (but not exactly the same phrase??) Note: at the marriage of his daughter Rose to Edward Cause: Witness at marriage of daughter Rose The other 2 are for 'Informant' events (e.g. informants of the death), but in both of these, the Note is empty (although I am sure I entered text in them, and this extra text is now in the Clause). Cause: Informant at death of father William The sentence of Informant is as follows:{individual} was the {label} {date} {place} <{note}> so that when the Note is blank, the sentence just reads "He was the informant on 24 Jan 1918 in Oxford", so I don't understand where the Cause is getting the (correct) information of 'at death of father William' from (though again I am sure I originally entered this in the Note. Any ideas welcome - meanwhile I will be checking all my other witness and informant facts!   Regards, Andrea ________________________________ From: Simon Orde <simon-fhu@family-historian.co.uk> To: FHU Mailing List <FAMILY-HISTORIAN-USERS-L@rootsweb.com> Sent: Wednesday, 8 February 2012, 10:29 Subject: [FHU] *** Duplicated 'Cause' Bug We have just discovered a bug that is present in the current version (4.1) of Family Historian (thank you to Roger and Graham for pointing this out). The bug is associated with the "Cause" box on the Facts tab of the Property Box.  Ordinarily you won't see a Cause box in the Facts tab.  It only appears if you select certain types of event - e.g. death.  The symptom of the bug is that in certain circumstances, the value of the Cause box can be copied (i.e. duplicated) to other events which don't usually have a cause associated with them - such as birth or burial. The bug happens, and *only* happens, if the cursor is in the Cause Box of the Facts tab of the Property Box, when you do certain things.  For example, if at this point you click on the 'Go Back', 'Go Foward' or 'Up' buttons on the Property Box toolbar, the value in the Cause field will be copied to the first event of the record you navigate to, *if* that event is an event like Birth which can have a cause, but doesn't usually have one, and which doesn't get a Cause box in the Facts tab. If the first event is an event like Death which does get a Cause box in the Facts tab, the bug does not occur. If you think you might have been affected, you can download a query from the FHUG downloads area (www.fhug.org.uk) called "Non_Death_Facts_With_Causes". This lists all recorded causes for all events except death events (death causes won't ever have an invalid value).  Don't assume that because a Cause for an event is listed, it is necessarily a wrong value.  It may be a valid cause (e.g. a divorce or retirement cause).  But if you see any cause values that look wrong, you can easily delete them by clicking on the cell in the 'Cause' column and pressing the Delete key - and then confirm if asked if you want to delete the field in question.  As always, take backups to be safe, before doing anything you might regret. We apologise for any inconvenience caused.  The bug will be fixed in version 5.  Meanwhile, you can prevent this bug happening by not leaving the cursor in the Cause box of the Facts tab of the Property Box when you click on toolbar buttons or menu commands. Simon Orde List Administrator & Family Historian designer ------------------------------- 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 a delightfully obscure bug. This must have caused some head scratching. Thanks for the explanation and the corrective action. I found and eliminated errors in three of my eight major projects. Peter

We have just discovered a bug that is present in the current version (4.1) of Family Historian (thank you to Roger and Graham for pointing this out). The bug is associated with the "Cause" box on the Facts tab of the Property Box. Ordinarily you won't see a Cause box in the Facts tab. It only appears if you select certain types of event - e.g. death. The symptom of the bug is that in certain circumstances, the value of the Cause box can be copied (i.e. duplicated) to other events which don't usually have a cause associated with them - such as birth or burial. The bug happens, and *only* happens, if the cursor is in the Cause Box of the Facts tab of the Property Box, when you do certain things. For example, if at this point you click on the 'Go Back', 'Go Foward' or 'Up' buttons on the Property Box toolbar, the value in the Cause field will be copied to the first event of the record you navigate to, *if* that event is an event like Birth which can have a cause, but doesn't usually have one, and which doesn't get a Cause box in the Facts tab. If the first event is an event like Death which does get a Cause box in the Facts tab, the bug does not occur. If you think you might have been affected, you can download a query from the FHUG downloads area (www.fhug.org.uk) called "Non_Death_Facts_With_Causes". This lists all recorded causes for all events except death events (death causes won't ever have an invalid value). Don't assume that because a Cause for an event is listed, it is necessarily a wrong value. It may be a valid cause (e.g. a divorce or retirement cause). But if you see any cause values that look wrong, you can easily delete them by clicking on the cell in the 'Cause' column and pressing the Delete key - and then confirm if asked if you want to delete the field in question. As always, take backups to be safe, before doing anything you might regret. We apologise for any inconvenience caused. The bug will be fixed in version 5. Meanwhile, you can prevent this bug happening by not leaving the cursor in the Cause box of the Facts tab of the Property Box when you click on toolbar buttons or menu commands. Simon Orde List Administrator & Family Historian designer

Free software? You get what you pay for Nick Sent from my iPhone On 7 Feb 2012, at 16:50, Bob Margolis <bob.margolis@ntlworld.com> wrote: > Martin was using Wine (free) not Parallels, I think. > > Bob > > On 07/02/2012 16:29, Gerry Newnham wrote: >> Martin, >> >> I am running Family Historian version 4 on a Mac with Parallels and have had no trouble with the Mac freezing. You might wish to consider upgrading. Incidentally, Ancestral Sources also works extremely well under Parallels. >> >> Regards, >> >> Gerry >> >> ------------------------------- >> 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 >> > > ------------------------------- > 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 >

I am rather upset by this email from 'Robacis'. If Ancestral Sources did indeed corrupt your file why on earth have you not made any kind of contact with me to let me know? On the help menu of Ancestral Sources there are links to email for support and also to go the Ancestral Sources forum to ask for help. I don't use this mailing list - it is a Calico Pie mailing list and A.S. is not a Calico Pie product so it would be wrong of me to use it for support and I *really* don't want to upset Calico. I hope they'll forgive me for answering this one. I have just this afternoon been informed that you've emailed all the people on the list to warn them about using Ancestral Sources, suggesting it does nasty things losing multimedia, etc. This seems very unfair when I've been given no chance at all to investigate it or prove/disprove the claim. If indeed there is a problem then I should be able to fix it. I haven't had any similar reports that I can remember with Version 2 of Ancestral Sources. It certainly isn't 'essential' to run the Census Date Check before entering data into Ancestral Sources. You only need to do this if you are allocating census flags. Ancestral Sources (and Gedcom Census before it) is something that I spend a lot of time working on in my limited spare time, I provide it free of charge (though many people kindly donate money) and I go out of my way to help people who ask for support. For example, on several occasions in the past I've even sent people their own unique version of my software just to solve a particular issue for them ahead of an 'official' release. Perhaps Robert you could send me some information about what went wrong and maybe a copy of a GEDCOM file that can illustrate the problem that you had so that I can investigate further, and if AS does have a problem I can try to fix it in Version 3 which should be out soon. Nick -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Robert Sent: 07 February 2012 12:01 To: FAMILY-HISTORIAN-USERS@rootsweb.com Subject: [FHU] Problem with flags Some weeks ago I raised the issue of Ancestral Sources apparently corrupting the FH gedcom file and doing some nasty things such a losing some multimedia from FH. Some kind contributors mentioned various ways to solve the problem and I grateful for the suggestions, but to no avail. I now seem to have solved the problem so this message for the benefit of those who find themselves in the same position. It stems from the fact that the original gedcom file was created in Family Tree Maker and the Census dates were shown as the year of the census not the actual date. Ancestral Sources seemed not to like this and hence corrupted the file. The solution is to run "Census date check" in Ancestral Sources before trying to update the flags. by saving the Census data. Having run this check and reallocated the censuses by the actual date, once this had been done Ancestral Sources happily updated the gedcom file correctly and all the correct flags were shown in FH. So for anyone importing a file to FH or anyone using AS for the first time it seems essential to run this check before trying to input data Robacis

Martin was using Wine (free) not Parallels, I think. Bob On 07/02/2012 16:29, Gerry Newnham wrote: > Martin, > > I am running Family Historian version 4 on a Mac with Parallels and have had no trouble with the Mac freezing. You might wish to consider upgrading. Incidentally, Ancestral Sources also works extremely well under Parallels. > > Regards, > > Gerry > > ------------------------------- > 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 >

Many thanks Mike, that works a treat. Dave, I do not have a shortcut to listing Siblings, but the following technique will automatically omit the Individual themselves. Use the function expression below for each entry, and replace [1] with [2] et seq in two places in each one. =TextIf(IsSameItem(%INDI%,%INDI.FAMC[1]>CHIL[1]>%),"",%INDI.FAMC[1]>CHIL[1]> %) =TextIf(IsSameItem(%INDI%,%INDI.FAMC[1]>CHIL[2]>%),"",%INDI.FAMC[1]>CHIL[2]> %) ... =TextIf(IsSameItem(%INDI%,%INDI.FAMC[1]>CHIL[19]>%),"",%INDI.FAMC[1]>CHIL[19 ]>%) It works by testing if %INDI% is the same as the Sibling, and if so produces "" empty string, otherwise the Sibling. Regards, Mike Tate -----Original Message----- From: family-historian-users-bounces@rootsweb.com [mailto:family-historian-users-bounces@rootsweb.com] On Behalf Of Dave Simpson Sent: 07 February 2012 12:00 To: FAMILY-HISTORIAN-USERS-L@rootsweb.com Subject: [FHU] Individual Summary Report - Sibling List Individual Summary Report - Sibling List Does anyone know of a simple way of reporting a list of a person's siblings in this report? I have used a somewhat clumsy method so far that lists all children of the family: %INDI.FAMC[1]>CHIL[1]>% %INDI.FAMC[1]>CHIL[2]>% .... %INDI.FAMC[1]>CHIL[19]>% I have to have 19 entries to make sure that all siblings are listed (max is 18 to date), albeit that they are hidden when they don't exist. Unfortunately this duplicates the individual themselves which is what I would like to avoid (i.e. if the individual is child 4 the I don't want child 4 to appear in the Sibling list Any suggestions gratefully received Dave

Martin, I am running Family Historian version 4 on a Mac with Parallels and have had no trouble with the Mac freezing. You might wish to consider upgrading. Incidentally, Ancestral Sources also works extremely well under Parallels. Regards, Gerry

Simon, I don't know whether it got through to you but I had a problem with BC dates (FH4): ages came out negative. Jane had a look and agreed it was a bug. Also, I have switched from a PC (running latest version of FH4) to a MAC but can only run FH 3.1.2 using the CrossOver/Wine emulator. I cannot upgrade to FH4 on the MAC because it freezes after I've entered the upgrade Key. I suspect it it trying to access the internet and not finding it. The CrossOver forum does suggest a work around but it's a bit messy (the trial version installs but doesn't run). Can you suggest a fix? I'm concerned that if I buy FH5 it may not work or, if it does, future upgrades may not work. Thanks, Best wishes (I like your program!) Martin Cragg Cheshire On 12-02-06 12:28 PM, Simon Orde wrote: > There have been some posts asking when version 5 will be released. We had > said February, but at this point it's looking like March. I'm sorry about > that. We will of course release it as soon as it's ready - but no sooner. > Thank you all for your patience. > > Simon Orde > Calico Pie > > > ------------------------------- > 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 >

Alternatively, you can keep all your 'possible' in your main database, still entering them as an 'unrelated individual', or in 'orphan' family groups where you can identify them as such. You can report on them using the 'Search for Orphans' standard query, or perhaps using the =RelationPool function. I have also defined and set a 'Tentative' flag against any such dubious/uncertain individuals, and use this to condition how they are displayed in diagrams. I also add a record level note describing why they are dubious/uncertain and what needs to be done to confirm/reject them. HTH John