Re: [LegacyUG] importing from paf
Arlene,Legacy will import from the regular PAF database but it does not import a PAF zipped backup file. If you only have the backup file, you will have to import it to PAF and then have Legacy import it directly from the PAF file or use PAF to make a GEDCOM. The direct import is much easier. One thing that I recommend before importing from a PAF file is to have PAF do a check/repair because many times there are structural flaws which should be fixed before trying to use the PAF data.Ron Taylor --- On Thu, 4/18/13, Arlene wrote: From: Arlene Subject: [LegacyUG] importing from paf To: LegacyUserGroup@LegacyUsers.com Date: Thursday, April 18, 2013, 4:08 PM I was helping a patron at our family history center today convert his PAF file to legacy. I went to import from PAF and Legacy could not find PAF backup (zip) file. I finally had to make a gedcom to import. What was I doing wrong?Arlene from Utah Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
[LegacyUG] importing from paf
I was helping a patron at our family history center today convert his PAF file to legacy. I went to import from PAF and Legacy could not find PAF backup (zip) file. I finally had to make a gedcom to import. What was I doing wrong? Arlene from Utah Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Writer
Brian, Basically sources are not reproduced correctly in other software (ie not Legacy) because of incompatibility between the GEDCOM and the software, It mainly affects those of us who use other software for webpages. I use SW and put up with the problem. Legacy is not on its own FTM, and my be other, software have the same problem. Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: Brian L. Lightfoot Sent: Thursday, April 18, 2013 8:52 PM To: LegacyUserGroup@LegacyUsers.com Subject: RE: [LegacyUG] Source Writer I'd be curious to know exactly what problems you and others are experiencing in the creation of a GEDCOM from SW. Or am I misunderstanding what you are saying? My understanding of what Sherry is cautioning about is that if you then take that same GEDCOM and re-import it back into Legacy, the SW format is lost and everything is converted to the Basic format. That is understandable but I don't know why or when anyone would want to do that. As Sherry said, a GEDCOM is not your first choice for creating a Legacy backup but in a case of last resort, it would still have all the data there. I'm getting the impression that some people are staying away from the SW format because they think it somehow screws up a GEDCOM report. There is only one issue that I have noticed in the creation of my own GEDCOM using SW sources. For some reason, the REPO (Repository) element remains even though the GEDCOM template I'm using has excluded the REPO element. I'm not sure if this is the fault of GEDCOM or if the Legacy customization menu for GEDCOMs is slightly defective. Not really a big issue either way. Brian in California -Original Message- From: Ron Ferguson [mailto:ronfergy@tiscali.co.uk] Sent: Thursday, April 18, 2013 12:01 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Sherry, Whilst what you say is accurate, many of us do export using a GEDCOM for publication of our websites. I appreciate that this is a GEDCOM problem rather than Legacy's. Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: Sherry/Support Sent: Thursday, April 18, 2013 7:46 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Everything you enter should be included in the gedcom. It's just that when you import the gedcom into Legacy, the sources will show in the "Basic" format rather than SourceWriter format. But, unless you're going back to an earlier version of Legacy which doesn't support SourceWriter anyway, you wouldn't use a gedcom to move a file from Legacy to Legacy. You'd do a backup and restore (File > Backup Family File). The gedcom should only be used for moving data into a different program or uploading to a website. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: > Here is my dilemma: I would like to use Source Writer for my sourcing > in Legacy to be sure that I've sourced according to standards. But > now I've heard that the data produced using Source Writer doesn't > always translate correctly into Gedcom. What do other people do? > Barbara Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
RE: [LegacyUG] Source Writer
I'd be curious to know exactly what problems you and others are experiencing in the creation of a GEDCOM from SW. Or am I misunderstanding what you are saying? My understanding of what Sherry is cautioning about is that if you then take that same GEDCOM and re-import it back into Legacy, the SW format is lost and everything is converted to the Basic format. That is understandable but I don't know why or when anyone would want to do that. As Sherry said, a GEDCOM is not your first choice for creating a Legacy backup but in a case of last resort, it would still have all the data there. I'm getting the impression that some people are staying away from the SW format because they think it somehow screws up a GEDCOM report. There is only one issue that I have noticed in the creation of my own GEDCOM using SW sources. For some reason, the REPO (Repository) element remains even though the GEDCOM template I'm using has excluded the REPO element. I'm not sure if this is the fault of GEDCOM or if the Legacy customization menu for GEDCOMs is slightly defective. Not really a big issue either way. Brian in California -Original Message- From: Ron Ferguson [mailto:ronfergy@tiscali.co.uk] Sent: Thursday, April 18, 2013 12:01 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Sherry, Whilst what you say is accurate, many of us do export using a GEDCOM for publication of our websites. I appreciate that this is a GEDCOM problem rather than Legacy's. Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: Sherry/Support Sent: Thursday, April 18, 2013 7:46 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Everything you enter should be included in the gedcom. It's just that when you import the gedcom into Legacy, the sources will show in the "Basic" format rather than SourceWriter format. But, unless you're going back to an earlier version of Legacy which doesn't support SourceWriter anyway, you wouldn't use a gedcom to move a file from Legacy to Legacy. You'd do a backup and restore (File > Backup Family File). The gedcom should only be used for moving data into a different program or uploading to a website. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: > Here is my dilemma: I would like to use Source Writer for my sourcing > in Legacy to be sure that I've sourced according to standards. But > now I've heard that the data produced using Source Writer doesn't > always translate correctly into Gedcom. What do other people do? > Barbara Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Writer
Barbara, Some people don't use SW for this reason. I use it, but when I share my data with a distant cousin via GEDCOM, I warn them that some of the source citations will appear a bit garbled. There have been discussions about this, which you can find in the LUG archive. The problem varies with the nature of the source template. Many templates compose the citation by interspersing data from the master source and the detail source fields. When Legacy exports such a source citation to GEDCOM, all the master fields are together, followed by all the detail fields. So the resulting citation reads a bit scrambled, and there can be issues with punctuation and with label words that weren't part of the actual data. You can experiment to see what it does to your data. (I have long maintained that Legacy developers could create an optional workaround to this limitation of the GEDCOM standard. The citation could be formatted as if for printing and then written to GEDCOM as a basic-style source detail. This would be helpful for one-way transfers.) Ward -Original Message- From: Sherry/Support Sent: Thursday, April 18, 2013 3:14 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Right - that's included in my comments about exporting to another program or uploading to a website. My point was that if you're sharing a file "Legacy to Legacy", unless you're going back to an earlier version of Legacy, you wouldn't use a gedcom. And previous versions wouldn't support the SourceWriter anyway. The important thing is that the information is exported and *should* be imported by the program you're using. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 12:00 PM, Ron Ferguson wrote: > Sherry, > > Whilst what you say is accurate, many of us do export using a GEDCOM for > publication of our websites. I appreciate that this is a GEDCOM problem > rather than Legacy's. > > Ron Ferguson > http://www.fergys.co.uk/ > > -Original Message- > From: Sherry/Support > Sent: Thursday, April 18, 2013 7:46 PM > To: LegacyUserGroup@LegacyUsers.com > Subject: Re: [LegacyUG] Source Writer > > Everything you enter should be included in the gedcom. It's just that > when you import the gedcom into Legacy, the sources will show in the > "Basic" format rather than SourceWriter format. > > But, unless you're going back to an earlier version of Legacy which > doesn't support SourceWriter anyway, you wouldn't use a gedcom to move > a file from Legacy to Legacy. You'd do a backup and restore (File > > Backup Family File). The gedcom should only be used for moving data > into a different program or uploading to a website. > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: >> Here is my dilemma: I would like to use Source Writer for my sourcing >> in Legacy to be sure that I've sourced according to standards. But now >> I've heard that the data produced using Source Writer doesn't always >> translate correctly into Gedcom. What do other people do? >> Barbara > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Writer
Right - that's included in my comments about exporting to another program or uploading to a website. My point was that if you're sharing a file "Legacy to Legacy", unless you're going back to an earlier version of Legacy, you wouldn't use a gedcom. And previous versions wouldn't support the SourceWriter anyway. The important thing is that the information is exported and *should* be imported by the program you're using. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 12:00 PM, Ron Ferguson wrote: > Sherry, > > Whilst what you say is accurate, many of us do export using a GEDCOM for > publication of our websites. I appreciate that this is a GEDCOM problem > rather than Legacy's. > > Ron Ferguson > http://www.fergys.co.uk/ > > -Original Message- > From: Sherry/Support > Sent: Thursday, April 18, 2013 7:46 PM > To: LegacyUserGroup@LegacyUsers.com > Subject: Re: [LegacyUG] Source Writer > > Everything you enter should be included in the gedcom. It's just that > when you import the gedcom into Legacy, the sources will show in the > "Basic" format rather than SourceWriter format. > > But, unless you're going back to an earlier version of Legacy which > doesn't support SourceWriter anyway, you wouldn't use a gedcom to move > a file from Legacy to Legacy. You'd do a backup and restore (File > > Backup Family File). The gedcom should only be used for moving data > into a different program or uploading to a website. > > > Sincerely, > Sherry > Technical Support > Legacy Family Tree > > > On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: >> Here is my dilemma: I would like to use Source Writer for my sourcing >> in Legacy to be sure that I've sourced according to standards. But now >> I've heard that the data produced using Source Writer doesn't always >> translate correctly into Gedcom. What do other people do? >> Barbara > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Writer
Sherry, Whilst what you say is accurate, many of us do export using a GEDCOM for publication of our websites. I appreciate that this is a GEDCOM problem rather than Legacy's. Ron Ferguson http://www.fergys.co.uk/ -Original Message- From: Sherry/Support Sent: Thursday, April 18, 2013 7:46 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Everything you enter should be included in the gedcom. It's just that when you import the gedcom into Legacy, the sources will show in the "Basic" format rather than SourceWriter format. But, unless you're going back to an earlier version of Legacy which doesn't support SourceWriter anyway, you wouldn't use a gedcom to move a file from Legacy to Legacy. You'd do a backup and restore (File > Backup Family File). The gedcom should only be used for moving data into a different program or uploading to a website. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: > Here is my dilemma: I would like to use Source Writer for my sourcing > in Legacy to be sure that I've sourced according to standards. But now > I've heard that the data produced using Source Writer doesn't always > translate correctly into Gedcom. What do other people do? > Barbara Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Source Writer
Everything you enter should be included in the gedcom. It's just that when you import the gedcom into Legacy, the sources will show in the "Basic" format rather than SourceWriter format. But, unless you're going back to an earlier version of Legacy which doesn't support SourceWriter anyway, you wouldn't use a gedcom to move a file from Legacy to Legacy. You'd do a backup and restore (File > Backup Family File). The gedcom should only be used for moving data into a different program or uploading to a website. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 11:12 AM, Barbara wrote: > Here is my dilemma: I would like to use Source Writer for my sourcing > in Legacy to be sure that I've sourced according to standards. But now > I've heard that the data produced using Source Writer doesn't always > translate correctly into Gedcom. What do other people do? > Barbara Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
[LegacyUG] Source Writer
Here is my dilemma: I would like to use Source Writer for my sourcing in Legacy to be sure that I've sourced according to standards. But now I've heard that the data produced using Source Writer doesn't always translate correctly into Gedcom. What do other people do? Barbara Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Gensmarts 2.0
Has GenSmarts 2.0 added Findagrave to their list of sites? > >Thanks > >Morris Sonnier Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Best way to record a divorce
I record Divorce records under the Marriage Information/Event/Divorce and keep it simple. I know all researchers handle situations differently, but I personally like to leave some things private, so I included [[ -- ]] on information I want for myself, but not others. I also do this when I record Death Certificate information, such as suicides. Both families are hurt by these actions and as a researcher, I don't want to stir up old wounds, my goal is to honor those in my database. Syble Families Researching: Cline/Klein, Daniel, Newton, Witherspoon, Perryman, Gilbreath, Lindsey, Brown, Foote, Curry, Fleming, Glasscock, Edwards, Waters, Wheat > > From: Tony Rolfe >To: LegacyUserGroup@LegacyUsers.com >Sent: Wednesday, April 17, 2013 11:49 PM >Subject: [LegacyUG] Best way to record a divorce > > >I have just downloaded a set of divorce papers and was wondering what is >the best way to record this. > >There is a standard "Divorce Filing" event, but that doesn't cover a >fraction of the information available. > >I have the date of the petition, the date of the decree Nisi and the >date of the final decree, as well as details on the grounds of the >petition and the respondent's response. > >I'm thinking of putting the standard event in the wife's events, since >she petitioned for the divorce. Then I'll create a new event for the >Divorce Decrees, so I can record those dates. These would be marriage >events. > >Does this sound reasonable and is there anything I've missed? > >Thanks > >Tony > > > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.legacyfamilytree.com/). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Best way to record a divorce
On 18/04/2013 05:49, Tony Rolfe wrote: > I have just downloaded a set of divorce papers and was wondering what is > the best way to record this. > > There is a standard "Divorce Filing" event, but that doesn't cover a > fraction of the information available. > > I have the date of the petition, the date of the decree Nisi and the > date of the final decree, as well as details on the grounds of the > petition and the respondent's response. > > I'm thinking of putting the standard event in the wife's events, since > she petitioned for the divorce. Then I'll create a new event for the > Divorce Decrees, so I can record those dates. These would be marriage > events. > > Does this sound reasonable and is there anything I've missed? I entered a Divorce Event under Marriage Events for the couple concerned. The EventName was "Divorce", the Desc "Decree Absolute" and the Date that of the Decree. I added some details as Notes and the final sentence reads "Divorce: on 29 July 1884 John and Sarah were granted a Decree Absolute. John had filed a petition for Divorce on 18 January 1883 and a Decree Nisi was granted on 23 January 1884 on the grounds of Sarah's adultery with unknown men." The various documents are attached to the Source and can be printed out in full and included with a Report if necessary. For most purposes that is sufficient detail. -- Jenny M Benson Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
Re: [LegacyUG] Best way to record a divorce
Tony, For recording a divorce there is only the Marriage Status entry. If you wish to include all the details (which generally I don't) then I would probably do something along the lines you suggest, but rather than create a Spouse Divorce Event I think that I would create a Marriage Divorce Event. --- Ron Ferguson http://www.fergys.co.uk/ GOONS #5307 "Tony Rolfe" wrote: >I have just downloaded a set of divorce papers and was wondering what is >the best way to record this. > >There is a standard "Divorce Filing" event, but that doesn't cover a >fraction of the information available. > >I have the date of the petition, the date of the decree Nisi and the >date of the final decree, as well as details on the grounds of the >petition and the respondent's response. > >I'm thinking of putting the standard event in the wife's events, since >she petitioned for the divorce. Then I'll create a new event for the >Divorce Decrees, so I can record those dates. These would be marriage >events. > >Does this sound reasonable and is there anything I've missed? > >Thanks > >Tony > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
