I have just created a new file for my family, exporting data from a Master File I started when I first started research. The Master File is now about 32,000 individuals and includes many, many people who are not remotely related to me. I included neighbors of my ancestors, thinking that I might develop new marriage ties. Way back when people never went very far to find spouses. I'm now starting a new file that includes only those folks who are related to me, either by blood or by marriage. I'm doing it by export from the Master and importing into the new file. That's were my source data problems starts. Because of the size of the Master File, I developed a method of using a single source title for a given source. This was done so my Source List would not contain thousands of entries. An example is marriage records. I entered only a few source titles for it; like Marriage Records, DeWitt County, IL. I titled it this way, completed everything except the Citation Detail section and saved it. Then, when I found a new individual who was married there, I brought up that source and completed the Citation Detail section; copy of the marriage license (if I got it) or the Marriage Index, including Book & Page # where the license was located. Since I have over a hundred marriages in that county, I was able to have only one source title, rather than over 100, in my source list. I did the same with almost all of my sources, such as death records, cemetery headstone readings, census records, etc. This limited my source list to about 400 titles, rather than over 100,000 (assuming 3 sources for each person and I know it would be a lot more that 3 per person). This is the problem. After the export/import, the new file has 1550 entries on the Source List for a file that has only 3200 people in it. That is 400 titles for 32,000 names vs. 1,550 titles for on 3,200 people. I've figured out what happened. For the individuals exported/imported, each source was imported as a new source title; (i.e. everyone with a marriage in DeWitt County in the Master File(about 100 of them) had 1 Source title, with different Citation Details for each) and in the new database that came out to about 100 source titles, all the same Title and the individual citation details. When I go to Edit the Source List, I can't figure out which Source goes with which individual. Even if I could, I can't figure a way to get all 100 of them down to a single title with 100 different citation detail entries. I'm not sure if merging sources will merge all entries with the same title and repository. If it does then the source on everyone will have the same citation detail and only 1 of the 100 will be correct. If it merges them only when the title, repository and citation detail match, then I'll still have the 100 source titles in my source list. I hope this explanation of my problem is coherent and understandable. Can someone explain to me how I can get the new database to have only one Marriage Records for DeWitt County in the new database file Source List and still have the correct Citation Detail in the individual records for folks married in the county? The problem exists for almost every source title in Master File database. Thanks for any help I can get. Dick Cazier Lakewood, CO

I agree with everyone else. I go one step further though. I'm doing my family history for my grandchildren, so I go up from their lines. Yes, it's more work, but, I'm about the only one doing any family history on both sides. I keep it all in one database. SueM Dick Cazier wrote: > Mary, > I agree with the advice of everyone, keep one file that includes both your > and your husband's families. > >

I agree that one file works best, with the exception of the two-people, two-computer scenario Lynn mentions. When I started researching another family with my focus surname, expecting that they would link, I started a separate file. The link has not been found but if and when it is, I will import the smaller file into the larger one by Gedcom. Lila ----- Original Message ----- From: <lem[email protected]> To: <[email protected]> Sent: 29 March, 2008 4:50 PM Subject: Re: [PAF-5] Question > Mary, > I'm a firm beliver that a husbands and wifes data, all of their > descendants data, and all of both of their ancestors data should be in the > same file. This allows me to print full pedigree charts for my children. > I suppose that if this file ever gets too large (what ever that number > is), it would be benificial to split the file. Also, if the husband and > wife both work on their data on different computers at the same time, it > may be best to split the file. My main file contains over 35,000 > individuals. It's not yet too large. But then I'm prejudiced because I > also like to use the "GenCharts for PAF" program that prints special lists > and charts using MRINs as well as RINs from your PAF 5 data file. If I > used separate files I would only get half of some of those charts. > Lynn > >> ----- Original Message ----- >> From: "Mary Gagne" <[email protected]> >> To: [email protected] >> Subject: [PAF-5] Question >> Date: Sat, 29 Mar 2008 16:18:31 -0600 >> >> >> Is it advisable to make a separate file when working on my husband's >> family? I have one PAF, starting with me and going back on both >> parent's sides. Now I want to do the same thing with my husband in >> place "one". Separate PAFs the best way to go? >> >> Mary >> >> >> >> ------------------------------- >> To unsubscribe from the list, please send an >> email to [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

Mary, I'm a firm beliver that a husbands and wifes data, all of their descendants data, and all of both of their ancestors data should be in the same file. This allows me to print full pedigree charts for my children. I suppose that if this file ever gets too large (what ever that number is), it would be benificial to split the file. Also, if the husband and wife both work on their data on different computers at the same time, it may be best to split the file. My main file contains over 35,000 individuals. It's not yet too large. But then I'm prejudiced because I also like to use the "GenCharts for PAF" program that prints special lists and charts using MRINs as well as RINs from your PAF 5 data file. If I used separate files I would only get half of some of those charts. Lynn > ----- Original Message ----- > From: "Mary Gagne" <[email protected]> > To: [email protected] > Subject: [PAF-5] Question > Date: Sat, 29 Mar 2008 16:18:31 -0600 > > > Is it advisable to make a separate file when working on my husband's > family? I have one PAF, starting with me and going back on both > parent's sides. Now I want to do the same thing with my husband in > place "one". Separate PAFs the best way to go? > > Mary > > > > ------------------------------- > To unsubscribe from the list, please send an > email to PAF-5-USE[email protected] with > the word 'unsubscribe' without the quotes in > the subject and the body of the message >

I think the PAF issue has hopefully been addressed. However, the issue of PDF versus RTF may be an issue still. If you do not have Acrobat, you can still create PDFs with several 3rd party products. There are even some that allow editing at minimal cost. However, editing a PDF in any product is not really recommended. For editing, you should use WORD or something else that can read the RTF file. Unfortunately, the RTF files that are produced by PAF are not simple files, but are collections of text blocks. That also limits the amount of editing you can do. If you rather copy info from a PDF or RTF file, you can copy the information into a new word processor file and play as you wish. You will have to do all your own formating in such cases. A major disadvantage of sending WORD files around to others (not PDF) is the problem of the WORD reflow. Whenever the printer is changed in WORD, it reflows the document. That can change page breaks and many other format features. In addition, I usually see the RTF files open in WORD with the WORD Normal document defaults that has different margins. Thus margins have to be reset for the PAF created RTF files. That is not an issue with the PDF files. The whole idea of a PDF is that it will look and print the same on all systems. As far as posting a book on line, I would do it in PDF form. That is in large part due to the reflow problem with WORD, and the problem of others actually being able to import RTF files. Not everyone has RTF capability (i.e., not everyone owns or uses WORD). PDF files can be secured, but yes there are workarounds. However, the workarounds generally require a fair amount of knowledge and to a large extent your data is reasonably secure. To fully secure a document on line you are often talking in the order of thousands of dollars. If you object to the limitations of online security, the best thing is to not post your information unless you create a secure web site that you allow folks into that you trust. In terms of web pages, if you supply the files (either DOC, RTF, or PDF), it is simply a matter of posting them and adding a link. If the individual says a WORD file is easier to work with, then you must be asking him to do something with it. If they are just planning to post it, then there is no difference in the effort to use the document. I suggest you use what you are comfortable with, or ask for a better explanation - Unless he is doing something fancy there is no difference and something fancy is often not appreciated by web users and costs an arm and leg. If it is RTF files that you plan to post, then you have just limited the possible users to those with RTF capability. As I mentioned, not everyone can read RTFs. They are a MS hold over that were generally have had MS OFFICE compatibility, but not necessarily other compatibility. As I recall, several PAF users used to complain because they used Word Perfect (I think that was fixed in later versions of WP). Hope that gives you a useful alternate view and provides some useful information for others. Bill > I suppose there is a work-around. I work with a true Guru on occasion--he's > going to build a Website for me. I asked about supplying my book in Adobe or > Word, and he said Word is easier for him to work with. I expressed my > concern that my book could be so easily altered if it was in Word, and he > told me that there are programs for getting around Adobe's non-ability to be > changed, so anyone using such a program could change it anyway. > > Lila > > > Lila Said > >> 1. No capability of editing reports that are printed to file -- they > >> print > >> into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the > >> only > >> one who edits reports, possibly because it's a little tricky. After you > >> get > >> the idea, editing is quite easy. > > > > You are not the only one who edits reports. Is there a "work around" in AQ > > since I only have Acrobat Reader? > >

Mary, I agree with the advice of everyone, keep one file that includes both your and your husband's families. I would add a caution to everyone who is exporting information from one file to another, using GEDCOMs. It involves problems with the sources. I've just done some export/import operations and have encountered a huge problem. Shortly I'll be sending an email to all, asking for help in solving the problem. Dick Cazier Lakewood, CO ----- Original Message ----- From: "Mary Gagne" <[email protected]> To: <[email protected]> Sent: Saturday, March 29, 2008 4:18 PM Subject: [PAF-5] Question > Is it advisable to make a separate file when working on my husband's > family? I have one PAF, starting with me and going back on both > parent's sides. Now I want to do the same thing with my husband in > place "one". Separate PAFs the best way to go? > > Mary > > > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

Is it advisable to make a separate file when working on my husband's family? I have one PAF, starting with me and going back on both parent's sides. Now I want to do the same thing with my husband in place "one". Separate PAFs the best way to go? Mary

At 02:06 PM 3/29/2008 [email protected] wrote: >Message: 1 >Date: Sat, 29 Mar 2008 08:51:33 -1000 >From: "John Vilburn" <[email protected]> >Subject: [PAF-5] PAF End-of-Life Announcement - NOT >Gordon did not say PAF would no longer be supported. He also did not >say that you had to stop using PAF. > >PAF, BY ITSELF, will not work directly with NFS but that is OK >because FamilyInsight will act as the connection between PAF and >NFS. And if you >already have PAF Insight, FamilyInsight will be a regular update for >you. No need to do anything special. When FamilyInsight is released, >PAF Insight >will notify you that there is an update and ask if you want to install it. >FamilyInsight is one of the commercial programs that Gordon was referring to. > >So if you love PAF and want to keep using it, then go ahead and >continue. Ohana Software has you covered. Well, thats not completely true. I really love PafInsight. I have a data base that is about 200,000 individuals and it is too large to work with PAFInsight. Unless the new FamilyInsight will work with large data bases? Karen

Ann I'm with you, as I don't plan on changing my data from PAF. However I do like to use AQ or PAF Wiz for certain enhancements, but not to change the data from PAF. And I do agree with all the others about fantastic help from Gaylon. Ross GH Cotton, Burlington, ON, CAN 905)639-2929 Genealogy of the Cotton surname is my Enigma I haven't sent an attachment if the details are not mentioned above GOONS member responsible for tracking the family name, COTTON, #1437 Coordinator for Cotton DNA testing Project, Worldwide see http://home.comcast.net/~cottondna/ ----- Original Message ----- From: "Ann" <[email protected]> To: <[email protected]> Sent: Saturday, March 29, 2008 2:19 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > How does or will that effect anybody still wanting to carry on using paf > as > it is. > I have a database with 20,000 individuals in it from over 20 of research > and am happy as I am..Ok I am a stick in the mud but "end of life > announcements" surely don't actually mean that the programme stop working > just because there will be no more updates or enhancements to it. > > I for one, am happy without all the add ons,. > Ann > ----- Original Message ----- > From: "Richard Halliday" <[email protected]> > To: <[email protected]> > Sent: Saturday, March 29, 2008 5:40 PM > Subject: [PAF-5] PAF End-of-Life Announcement > > >> All; >> Yesterday I received the following from a friend. As a result I am >> now looking at Legacy and Ancestral Quest. My tentative conclusion is >> Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more >> familiar, it appears to handle the source citations better, its date >> modifiers (abt, bef, est, etc.) seem to be more familiar and it already >> has at least a partial interface with new FamilySearch. >> Comments? >> Richard L. Halliday >> West Linn, Oregon (where Winter Springs Right Back" {this >> morning's Oregonian}) >> "If the Lord wanted it done perfectly, >> He would not let me help." >> >> "Also at the conference,it was announced that a group of developers has >> created an extension to the PAF database file format allowing continued >> use of PAF files with the new capabilities of NFS. Commercial programs >> equipped with this extension will be able to support existing PAF files >> while simultaneously providing the advantages and new features of NFS." >> >> Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and >> John Vilburn (developer of PAF Insight). Ancestral Quest 12 already >> exploits some of the extensions when used in its "PAF mode". >> >> Gaylon made this presentation at the Developers Conference: >> [Wed., March 12] 11:00 Gaylon Findlay >> PAF SDK/ Sync (C++) >> The basic layout of the PAF 5 database structure will be covered, along >> with the basics of using the PAF 5 SDK provided by the Church. From this >> base, we will discuss the recent changes engineered by Incline Software >> and Ohana Software to allow syncing with the new FamilySearch Family >> Tree. http://ce.byu.edu/cw/cwgeneal/familysearch >> http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm >> >> "If you go here and scroll down to the schedule you will find links to >> the presentations. The presentations are available in PowerPoint, PDF or >> Adobe Connect. Adobe Connect gives you the screen capture with the audio >> portion of the presentation. The next best thing to being there." >> -Renee's Genealogy Blog : >> http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference >> >> >> --- Lesly Klippel <[email protected]: >> >> Subject: Future of PAF >> >> Here is an interesting item I found on the "Ancestry Insider" blog. >> >> Mike Benning >> >> ========================================== >> >> Gordon Clarke (Family History Department) read an official statement at >> the FamilySearch Developers Conference today announcing future migration >> paths available to users of the venerable PAF genealogy software. Once >> New FamilySearch (NFS) is fully available, PAF users will have several >> migration options available. Users can perform a one-time transfer of >> their data to NFS, which like PAF, will be free. Or users can purchase a >> commercial genealogy program, many of which are currently developing >> support for NFS. Also at the conference, it was announced that a group >> of developers has created an extension to the PAF database file format >> allowing continued use of PAF files with the new capabilities of NFS. >> Commercial programs equipped with this extension will be able to support >> existing PAF files while simultaneously providing the advantages and new >> features of NFS. >> >> The announcement is essentially an end-of-life announcement for PAF and >> puts to rest rumors that PAF was dead already as well as rumors that >> FamilySearch would make one more release of PAF with New FamilySearch >> support. >> >> ------------------------------- >> To unsubscribe from the list, please send an email to >> [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message

People seem to be doing okay with PAF's compatibility with Vista. The big question is, how long will PAF, without being updated, continue to work after Vista is superseded a couple of times? And as computers are replaced and new downloads of PAF are needed, will it still be available even after it's no longer being updated and/or supported? Lila ----- Original Message ----- From: "Ross G.H. Cotton" <[email protected]> To: "Ann" <[email protected]>; <[email protected]> Sent: 29 March, 2008 1:55 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > Ann > I'm with you, as I don't plan on changing my data from PAF. However I > do > like to use AQ or PAF Wiz for certain enhancements, but not to change the > data from PAF. > > And > I do agree with all the others about fantastic help from Gaylon. > > Ross GH Cotton, Burlington, ON, CAN 905)639-2929 > Genealogy of the Cotton surname is my Enigma > I haven't sent an attachment if the details are not mentioned above > > GOONS member responsible for tracking the family name, COTTON, #1437 > Coordinator for Cotton DNA testing Project, Worldwide > see http://home.comcast.net/~cottondna/ > ----- Original Message ----- > From: "Ann" <[email protected]> > To: <[email protected]> > Sent: Saturday, March 29, 2008 2:19 PM > Subject: Re: [PAF-5] PAF End-of-Life Announcement > > >> How does or will that effect anybody still wanting to carry on using paf >> as >> it is. >> I have a database with 20,000 individuals in it from over 20 of research >> and am happy as I am..Ok I am a stick in the mud but "end of life >> announcements" surely don't actually mean that the programme stop working >> just because there will be no more updates or enhancements to it. >> >> I for one, am happy without all the add ons,. >> Ann >> ----- Original Message ----- >> From: "Richard Halliday" <[email protected]> >> To: <[email protected]> >> Sent: Saturday, March 29, 2008 5:40 PM >> Subject: [PAF-5] PAF End-of-Life Announcement >> >> >>> All; >>> Yesterday I received the following from a friend. As a result I am >>> now looking at Legacy and Ancestral Quest. My tentative conclusion is >>> Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more >>> familiar, it appears to handle the source citations better, its date >>> modifiers (abt, bef, est, etc.) seem to be more familiar and it already >>> has at least a partial interface with new FamilySearch. >>> Comments? >>> Richard L. Halliday >>> West Linn, Oregon (where Winter Springs Right Back" {this >>> morning's Oregonian}) >>> "If the Lord wanted it done perfectly, >>> He would not let me help." >>> >>> "Also at the conference,it was announced that a group of developers has >>> created an extension to the PAF database file format allowing continued >>> use of PAF files with the new capabilities of NFS. Commercial programs >>> equipped with this extension will be able to support existing PAF files >>> while simultaneously providing the advantages and new features of NFS." >>> >>> Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and >>> John Vilburn (developer of PAF Insight). Ancestral Quest 12 already >>> exploits some of the extensions when used in its "PAF mode". >>> >>> Gaylon made this presentation at the Developers Conference: >>> [Wed., March 12] 11:00 Gaylon Findlay >>> PAF SDK/ Sync (C++) >>> The basic layout of the PAF 5 database structure will be covered, along >>> with the basics of using the PAF 5 SDK provided by the Church. From this >>> base, we will discuss the recent changes engineered by Incline Software >>> and Ohana Software to allow syncing with the new FamilySearch Family >>> Tree. http://ce.byu.edu/cw/cwgeneal/familysearch >>> http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm >>> >>> "If you go here and scroll down to the schedule you will find links to >>> the presentations. The presentations are available in PowerPoint, PDF or >>> Adobe Connect. Adobe Connect gives you the screen capture with the audio >>> portion of the presentation. The next best thing to being there." >>> -Renee's Genealogy Blog : >>> http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference >>> >>> >>> --- Lesly Klippel <[email protected]: >>> >>> Subject: Future of PAF >>> >>> Here is an interesting item I found on the "Ancestry Insider" blog. >>> >>> Mike Benning >>> >>> ========================================== >>> >>> Gordon Clarke (Family History Department) read an official statement at >>> the FamilySearch Developers Conference today announcing future migration >>> paths available to users of the venerable PAF genealogy software. Once >>> New FamilySearch (NFS) is fully available, PAF users will have several >>> migration options available. Users can perform a one-time transfer of >>> their data to NFS, which like PAF, will be free. Or users can purchase a >>> commercial genealogy program, many of which are currently developing >>> support for NFS. Also at the conference, it was announced that a group >>> of developers has created an extension to the PAF database file format >>> allowing continued use of PAF files with the new capabilities of NFS. >>> Commercial programs equipped with this extension will be able to support >>> existing PAF files while simultaneously providing the advantages and new >>> features of NFS. >>> >>> The announcement is essentially an end-of-life announcement for PAF and >>> puts to rest rumors that PAF was dead already as well as rumors that >>> FamilySearch would make one more release of PAF with New FamilySearch >>> support. >>> >>> ------------------------------- >>> To unsubscribe from the list, please send an email to >>> [email protected] 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 >> [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

Ann About every 2 weeks someone on the lists hears about the pending "death" of PAF and triggers a new round of discussion. The usual replies are: 1. PAF works fine with VISTA so we're all safe until we purchase a computer with an Operating System that PAF doesn't work on. 2. Just because the church will not update the software we all can continue to use it as is. I too am happy with PAF and don't plan to change in the near future. Bottom Line -- Don't Panic!! ----- Original Message ----- From: "Ann" <[email protected]> To: <[email protected]> Sent: Saturday, March 29, 2008 1:19 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > How does or will that effect anybody still wanting to carry on using paf > as > it is. > I have a database with 20,000 individuals in it from over 20 of research > and am happy as I am..Ok I am a stick in the mud but "end of life > announcements" surely don't actually mean that the programme stop working > just because there will be no more updates or enhancements to it. > > I for one, am happy without all the add ons,. > Ann > ----- Original Message ----- > From: "Richard Halliday" <[email protected]> > To: <[email protected]> > Sent: Saturday, March 29, 2008 5:40 PM > Subject: [PAF-5] PAF End-of-Life Announcement > > >> All; >> Yesterday I received the following from a friend. As a result I am >> now looking at Legacy and Ancestral Quest. My tentative conclusion is >> Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more >> familiar, it appears to handle the source citations better, its date >> modifiers (abt, bef, est, etc.) seem to be more familiar and it already >> has at least a partial interface with new FamilySearch. >> Comments? >> Richard L. Halliday >> West Linn, Oregon (where Winter Springs Right Back" {this >> morning's Oregonian}) >> "If the Lord wanted it done perfectly, >> He would not let me help." >> >> "Also at the conference,it was announced that a group of developers has >> created an extension to the PAF database file format allowing continued >> use of PAF files with the new capabilities of NFS. Commercial programs >> equipped with this extension will be able to support existing PAF files >> while simultaneously providing the advantages and new features of NFS." >> >> Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and >> John Vilburn (developer of PAF Insight). Ancestral Quest 12 already >> exploits some of the extensions when used in its "PAF mode". >> >> Gaylon made this presentation at the Developers Conference: >> [Wed., March 12] 11:00 Gaylon Findlay >> PAF SDK/ Sync (C++) >> The basic layout of the PAF 5 database structure will be covered, along >> with the basics of using the PAF 5 SDK provided by the Church. From this >> base, we will discuss the recent changes engineered by Incline Software >> and Ohana Software to allow syncing with the new FamilySearch Family >> Tree. http://ce.byu.edu/cw/cwgeneal/familysearch >> http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm >> >> "If you go here and scroll down to the schedule you will find links to >> the presentations. The presentations are available in PowerPoint, PDF or >> Adobe Connect. Adobe Connect gives you the screen capture with the audio >> portion of the presentation. The next best thing to being there." >> -Renee's Genealogy Blog : >> http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference >> >> >> --- Lesly Klippel <[email protected]: >> >> Subject: Future of PAF >> >> Here is an interesting item I found on the "Ancestry Insider" blog. >> >> Mike Benning >> >> ========================================== >> >> Gordon Clarke (Family History Department) read an official statement at >> the FamilySearch Developers Conference today announcing future migration >> paths available to users of the venerable PAF genealogy software. Once >> New FamilySearch (NFS) is fully available, PAF users will have several >> migration options available. Users can perform a one-time transfer of >> their data to NFS, which like PAF, will be free. Or users can purchase a >> commercial genealogy program, many of which are currently developing >> support for NFS. Also at the conference, it was announced that a group >> of developers has created an extension to the PAF database file format >> allowing continued use of PAF files with the new capabilities of NFS. >> Commercial programs equipped with this extension will be able to support >> existing PAF files while simultaneously providing the advantages and new >> features of NFS. >> >> The announcement is essentially an end-of-life announcement for PAF and >> puts to rest rumors that PAF was dead already as well as rumors that >> FamilySearch would make one more release of PAF with New FamilySearch >> support. >> >> ------------------------------- >> To unsubscribe from the list, please send an email to >> [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message

I suppose there is a work-around. I work with a true Guru on occasion--he's going to build a Website for me. I asked about supplying my book in Adobe or Word, and he said Word is easier for him to work with. I expressed my concern that my book could be so easily altered if it was in Word, and he told me that there are programs for getting around Adobe's non-ability to be changed, so anyone using such a program could change it anyway. Lila ----- Original Message ----- From: "Ken Guilette" <[email protected]> To: <[email protected]> Sent: 29 March, 2008 1:17 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > Lila Said >> 1. No capability of editing reports that are printed to file -- they >> print >> into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the >> only >> one who edits reports, possibly because it's a little tricky. After you >> get >> the idea, editing is quite easy. > > You are not the only one who edits reports. Is there a "work around" in AQ > since I only have Acrobat Reader? > > Regards > > Ken Guilette > South Barrington, IL USA > > ----- Original Message ----- > From: <[email protected]> > To: <[email protected]> > Sent: Saturday, March 29, 2008 1:06 PM > Subject: Re: [PAF-5] PAF End-of-Life Announcement > > >> Two problems with AQ, and as far as I know, all other software: >> >> 1. No capability of editing reports that are printed to file -- they >> print >> into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the >> only >> one who edits reports, possibly because it's a little tricky. After you >> get >> the idea, editing is quite easy. >> >> 2. No capability of switching languages. It's very nice to use the >> non-English-speaking cousin's native language for reports. All the clues >> are >> in the target language. Notes, of course, remain in the language in which >> they are written. >> >> It's hard to understand why the Family History Department would abandon >> PAF, >> after they have gone to the trouble of creating and supporting these >> excellent features. >> >> I second the comment about the great help that's available from Gaylon at >> AQ. >> >> Lila >> >> ----- Original Message ----- >> From: <[email protected]> >> To: <[email protected]> >> Sent: 29 March, 2008 12:47 PM >> Subject: Re: [PAF-5] PAF End-of-Life Announcement >> >> >>> >>> I believe either Legacy or Ancestral Quest would be a good choice.? >>> However, I believe I would go with AQ because of the great HELP that's >>> available from Gaylon. >>> >>> Howard Johnston >>> >>> >>> -----Original Message----- >>> From: Richard Halliday <[email protected]> >>> To: [email protected] >>> Sent: Sat, 29 Mar 2008 11:40 am >>> Subject: [PAF-5] PAF End-of-Life Announcement >>> >>> >>> >>> >>> All; >>> Yesterday I received the following from a friend. As a result I am >>> now looking at Legacy and Ancestral Quest. My tentative conclusion is >>> Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more >>> familiar, it appears to handle the source citations better, its date >>> modifiers (abt, bef, est, etc.) seem to be more familiar and it already >>> has at least a partial interface with new FamilySearch. >>> Comments? >>> Richard L. Halliday >>> West Linn, Oregon (where Winter Springs Right Back" {this >>> morning's Oregonian}) >>> "If the Lord wanted it done perfectly, >>> He would not let me help." >>> >>> "Also at the conference,it was announced that a group of developers has >>> created an extension to the PAF database file format allowing continued >>> use of PAF files with the new capabilities of NFS. Commercial programs >>> equipped with this extension will be able to support existing PAF files >>> while simultaneously providing the advantages and new features of NFS." >>> >>> Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and >>> John Vilburn (developer of PAF Insight). Ancestral Quest 12 already >>> exploits some of the extensions when used in its "PAF mode". >>> >>> Gaylon made this presentation at the Developers Conference: >>> [Wed., March 12] 11:00 Gaylon Findlay >>> PAF SDK/ Sync (C++) >>> The basic layout of the PAF 5 database structure will be covered, along >>> with the basics of using the PAF 5 SDK provided by the Church. From this >>> base, we will discuss the recent changes engineered by Incline Software >>> and Ohana Software to allow syncing with the new FamilySearch Family >>> Tree. http://ce.byu.edu/cw/cwgeneal/familysearch >>> http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm >>> >>> "If you go here and scroll down to the schedule you will find links to >>> the presentations. The presentations are available in PowerPoint, PDF or >>> Adobe Connect. Adobe Connect gives you the screen capture with the audio >>> portion of the presentation. The next best thing to being there." >>> -Renee's Genealogy Blog : >>> http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference >>> >>> >>> --- Lesly Klippel <[email protected]: >>> >>> Subject: Future of PAF >>> >>> Here is an interesting item I found on the "Ancestry Insider" blog. >>> >>> Mike Benning >>> >>> ========================================== >>> >>> Gordon Clarke (Family History Department) read an official statement at >>> the FamilySearch Developers Conference today announcing future migration >>> paths available to users of the venerable PAF genealogy software. Once >>> New FamilySearch (NFS) is fully available, PAF users will have several >>> migration options available. Users can perform a one-time transfer of >>> their data to NFS, which like PAF, will be free. Or users can purchase a >>> commercial genealogy program, many of which are currently developing >>> support for NFS. Also at the conference, it was announced that a group >>> of developers has created an extension to the PAF database file format >>> allowing continued use of PAF files with the new capabilities of NFS. >>> Commercial programs equipped with this extension will be able to support >>> existing PAF files while simultaneously providing the advantages and new >>> features of NFS. >>> >>> The announcement is essentially an end-of-life announcement for PAF and >>> puts to rest rumors that PAF was dead already as well as rumors that >>> FamilySearch would make one more release of PAF with New FamilySearch >>> support. >>> >>> ------------------------------- >>> To unsubscribe from the list, please send an email to >>> [email protected] >>> 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 >>> [email protected] 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 >> [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

I believe either Legacy or Ancestral Quest would be a good choice.? However, I believe I would go with AQ because of the great HELP that's available from Gaylon. Howard Johnston -----Original Message----- From: Richard Halliday <[email protected]> To: [email protected] Sent: Sat, 29 Mar 2008 11:40 am Subject: [PAF-5] PAF End-of-Life Announcement All; Yesterday I received the following from a friend. As a result I am now looking at Legacy and Ancestral Quest. My tentative conclusion is Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more familiar, it appears to handle the source citations better, its date modifiers (abt, bef, est, etc.) seem to be more familiar and it already has at least a partial interface with new FamilySearch. Comments? Richard L. Halliday West Linn, Oregon (where Winter Springs Right Back" {this morning's Oregonian}) "If the Lord wanted it done perfectly, He would not let me help." "Also at the conference,it was announced that a group of developers has created an extension to the PAF database file format allowing continued use of PAF files with the new capabilities of NFS. Commercial programs equipped with this extension will be able to support existing PAF files while simultaneously providing the advantages and new features of NFS." Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and John Vilburn (developer of PAF Insight). Ancestral Quest 12 already exploits some of the extensions when used in its "PAF mode". Gaylon made this presentation at the Developers Conference: [Wed., March 12] 11:00 Gaylon Findlay PAF SDK/ Sync (C++) The basic layout of the PAF 5 database structure will be covered, along with the basics of using the PAF 5 SDK provided by the Church. From this base, we will discuss the recent changes engineered by Incline Software and Ohana Software to allow syncing with the new FamilySearch Family Tree. http://ce.byu.edu/cw/cwgeneal/familysearch http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm "If you go here and scroll down to the schedule you will find links to the presentations. The presentations are available in PowerPoint, PDF or Adobe Connect. Adobe Connect gives you the screen capture with the audio portion of the presentation. The next best thing to being there." -Renee's Genealogy Blog : http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference --- Lesly Klippel <[email protected]: Subject: Future of PAF Here is an interesting item I found on the "Ancestry Insider" blog. Mike Benning ========================================== Gordon Clarke (Family History Department) read an official statement at the FamilySearch Developers Conference today announcing future migration paths available to users of the venerable PAF genealogy software. Once New FamilySearch (NFS) is fully available, PAF users will have several migration options available. Users can perform a one-time transfer of their data to NFS, which like PAF, will be free. Or users can purchase a commercial genealogy program, many of which are currently developing support for NFS. Also at the conference, it was announced that a group of developers has created an extension to the PAF database file format allowing continued use of PAF files with the new capabilities of NFS. Commercial programs equipped with this extension will be able to support existing PAF files while simultaneously providing the advantages and new features of NFS. The announcement is essentially an end-of-life announcement for PAF and puts to rest rumors that PAF was dead already as well as rumors that FamilySearch would make one more release of PAF with New FamilySearch support. ------------------------------- To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message

Lila Said > 1. No capability of editing reports that are printed to file -- they print > into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the > only > one who edits reports, possibly because it's a little tricky. After you > get > the idea, editing is quite easy. You are not the only one who edits reports. Is there a "work around" in AQ since I only have Acrobat Reader? Regards Ken Guilette South Barrington, IL USA ----- Original Message ----- From: <[email protected]> To: <[email protected]> Sent: Saturday, March 29, 2008 1:06 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > Two problems with AQ, and as far as I know, all other software: > > 1. No capability of editing reports that are printed to file -- they print > into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the > only > one who edits reports, possibly because it's a little tricky. After you > get > the idea, editing is quite easy. > > 2. No capability of switching languages. It's very nice to use the > non-English-speaking cousin's native language for reports. All the clues > are > in the target language. Notes, of course, remain in the language in which > they are written. > > It's hard to understand why the Family History Department would abandon > PAF, > after they have gone to the trouble of creating and supporting these > excellent features. > > I second the comment about the great help that's available from Gaylon at > AQ. > > Lila > > ----- Original Message ----- > From: <[email protected]> > To: <[email protected]> > Sent: 29 March, 2008 12:47 PM > Subject: Re: [PAF-5] PAF End-of-Life Announcement > > >> >> I believe either Legacy or Ancestral Quest would be a good choice.? >> However, I believe I would go with AQ because of the great HELP that's >> available from Gaylon. >> >> Howard Johnston >> >> >> -----Original Message----- >> From: Richard Halliday <[email protected]> >> To: [email protected] >> Sent: Sat, 29 Mar 2008 11:40 am >> Subject: [PAF-5] PAF End-of-Life Announcement >> >> >> >> >> All; >> Yesterday I received the following from a friend. As a result I am >> now looking at Legacy and Ancestral Quest. My tentative conclusion is >> Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more >> familiar, it appears to handle the source citations better, its date >> modifiers (abt, bef, est, etc.) seem to be more familiar and it already >> has at least a partial interface with new FamilySearch. >> Comments? >> Richard L. Halliday >> West Linn, Oregon (where Winter Springs Right Back" {this >> morning's Oregonian}) >> "If the Lord wanted it done perfectly, >> He would not let me help." >> >> "Also at the conference,it was announced that a group of developers has >> created an extension to the PAF database file format allowing continued >> use of PAF files with the new capabilities of NFS. Commercial programs >> equipped with this extension will be able to support existing PAF files >> while simultaneously providing the advantages and new features of NFS." >> >> Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and >> John Vilburn (developer of PAF Insight). Ancestral Quest 12 already >> exploits some of the extensions when used in its "PAF mode". >> >> Gaylon made this presentation at the Developers Conference: >> [Wed., March 12] 11:00 Gaylon Findlay >> PAF SDK/ Sync (C++) >> The basic layout of the PAF 5 database structure will be covered, along >> with the basics of using the PAF 5 SDK provided by the Church. From this >> base, we will discuss the recent changes engineered by Incline Software >> and Ohana Software to allow syncing with the new FamilySearch Family >> Tree. http://ce.byu.edu/cw/cwgeneal/familysearch >> http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm >> >> "If you go here and scroll down to the schedule you will find links to >> the presentations. The presentations are available in PowerPoint, PDF or >> Adobe Connect. Adobe Connect gives you the screen capture with the audio >> portion of the presentation. The next best thing to being there." >> -Renee's Genealogy Blog : >> http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference >> >> >> --- Lesly Klippel <[email protected]: >> >> Subject: Future of PAF >> >> Here is an interesting item I found on the "Ancestry Insider" blog. >> >> Mike Benning >> >> ========================================== >> >> Gordon Clarke (Family History Department) read an official statement at >> the FamilySearch Developers Conference today announcing future migration >> paths available to users of the venerable PAF genealogy software. Once >> New FamilySearch (NFS) is fully available, PAF users will have several >> migration options available. Users can perform a one-time transfer of >> their data to NFS, which like PAF, will be free. Or users can purchase a >> commercial genealogy program, many of which are currently developing >> support for NFS. Also at the conference, it was announced that a group >> of developers has created an extension to the PAF database file format >> allowing continued use of PAF files with the new capabilities of NFS. >> Commercial programs equipped with this extension will be able to support >> existing PAF files while simultaneously providing the advantages and new >> features of NFS. >> >> The announcement is essentially an end-of-life announcement for PAF and >> puts to rest rumors that PAF was dead already as well as rumors that >> FamilySearch would make one more release of PAF with New FamilySearch >> support. >> >> ------------------------------- >> To unsubscribe from the list, please send an email to >> [email protected] >> 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 >> [email protected] 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message

Two problems with AQ, and as far as I know, all other software: 1. No capability of editing reports that are printed to file -- they print into Adobe. PAF Print-to-File opens in Word. Sometimes I think I'm the only one who edits reports, possibly because it's a little tricky. After you get the idea, editing is quite easy. 2. No capability of switching languages. It's very nice to use the non-English-speaking cousin's native language for reports. All the clues are in the target language. Notes, of course, remain in the language in which they are written. It's hard to understand why the Family History Department would abandon PAF, after they have gone to the trouble of creating and supporting these excellent features. I second the comment about the great help that's available from Gaylon at AQ. Lila ----- Original Message ----- From: <[email protected]> To: <[email protected]> Sent: 29 March, 2008 12:47 PM Subject: Re: [PAF-5] PAF End-of-Life Announcement > > I believe either Legacy or Ancestral Quest would be a good choice.? > However, I believe I would go with AQ because of the great HELP that's > available from Gaylon. > > Howard Johnston > > > -----Original Message----- > From: Richard Halliday <[email protected]> > To: [email protected] > Sent: Sat, 29 Mar 2008 11:40 am > Subject: [PAF-5] PAF End-of-Life Announcement > > > > > All; > Yesterday I received the following from a friend. As a result I am > now looking at Legacy and Ancestral Quest. My tentative conclusion is > Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more > familiar, it appears to handle the source citations better, its date > modifiers (abt, bef, est, etc.) seem to be more familiar and it already > has at least a partial interface with new FamilySearch. > Comments? > Richard L. Halliday > West Linn, Oregon (where Winter Springs Right Back" {this > morning's Oregonian}) > "If the Lord wanted it done perfectly, > He would not let me help." > > "Also at the conference,it was announced that a group of developers has > created an extension to the PAF database file format allowing continued > use of PAF files with the new capabilities of NFS. Commercial programs > equipped with this extension will be able to support existing PAF files > while simultaneously providing the advantages and new features of NFS." > > Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and > John Vilburn (developer of PAF Insight). Ancestral Quest 12 already > exploits some of the extensions when used in its "PAF mode". > > Gaylon made this presentation at the Developers Conference: > [Wed., March 12] 11:00 Gaylon Findlay > PAF SDK/ Sync (C++) > The basic layout of the PAF 5 database structure will be covered, along > with the basics of using the PAF 5 SDK provided by the Church. From this > base, we will discuss the recent changes engineered by Incline Software > and Ohana Software to allow syncing with the new FamilySearch Family > Tree. http://ce.byu.edu/cw/cwgeneal/familysearch > http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm > > "If you go here and scroll down to the schedule you will find links to > the presentations. The presentations are available in PowerPoint, PDF or > Adobe Connect. Adobe Connect gives you the screen capture with the audio > portion of the presentation. The next best thing to being there." > -Renee's Genealogy Blog : > http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference > > > --- Lesly Klippel <[email protected]: > > Subject: Future of PAF > > Here is an interesting item I found on the "Ancestry Insider" blog. > > Mike Benning > > ========================================== > > Gordon Clarke (Family History Department) read an official statement at > the FamilySearch Developers Conference today announcing future migration > paths available to users of the venerable PAF genealogy software. Once > New FamilySearch (NFS) is fully available, PAF users will have several > migration options available. Users can perform a one-time transfer of > their data to NFS, which like PAF, will be free. Or users can purchase a > commercial genealogy program, many of which are currently developing > support for NFS. Also at the conference, it was announced that a group > of developers has created an extension to the PAF database file format > allowing continued use of PAF files with the new capabilities of NFS. > Commercial programs equipped with this extension will be able to support > existing PAF files while simultaneously providing the advantages and new > features of NFS. > > The announcement is essentially an end-of-life announcement for PAF and > puts to rest rumors that PAF was dead already as well as rumors that > FamilySearch would make one more release of PAF with New FamilySearch > support. > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] > 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 > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

All; Yesterday I received the following from a friend. As a result I am now looking at Legacy and Ancestral Quest. My tentative conclusion is Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more familiar, it appears to handle the source citations better, its date modifiers (abt, bef, est, etc.) seem to be more familiar and it already has at least a partial interface with new FamilySearch. Comments? Richard L. Halliday West Linn, Oregon (where Winter Springs Right Back" {this morning's Oregonian}) "If the Lord wanted it done perfectly, He would not let me help." "Also at the conference,it was announced that a group of developers has created an extension to the PAF database file format allowing continued use of PAF files with the new capabilities of NFS. Commercial programs equipped with this extension will be able to support existing PAF files while simultaneously providing the advantages and new features of NFS." Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and John Vilburn (developer of PAF Insight). Ancestral Quest 12 already exploits some of the extensions when used in its "PAF mode". Gaylon made this presentation at the Developers Conference: [Wed., March 12] 11:00 Gaylon Findlay PAF SDK/ Sync (C++) The basic layout of the PAF 5 database structure will be covered, along with the basics of using the PAF 5 SDK provided by the Church. From this base, we will discuss the recent changes engineered by Incline Software and Ohana Software to allow syncing with the new FamilySearch Family Tree. http://ce.byu.edu/cw/cwgeneal/familysearch http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm "If you go here and scroll down to the schedule you will find links to the presentations. The presentations are available in PowerPoint, PDF or Adobe Connect. Adobe Connect gives you the screen capture with the audio portion of the presentation. The next best thing to being there." -Renee's Genealogy Blog : http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference --- Lesly Klippel <[email protected]: Subject: Future of PAF Here is an interesting item I found on the "Ancestry Insider" blog. Mike Benning ========================================== Gordon Clarke (Family History Department) read an official statement at the FamilySearch Developers Conference today announcing future migration paths available to users of the venerable PAF genealogy software. Once New FamilySearch (NFS) is fully available, PAF users will have several migration options available. Users can perform a one-time transfer of their data to NFS, which like PAF, will be free. Or users can purchase a commercial genealogy program, many of which are currently developing support for NFS. Also at the conference, it was announced that a group of developers has created an extension to the PAF database file format allowing continued use of PAF files with the new capabilities of NFS. Commercial programs equipped with this extension will be able to support existing PAF files while simultaneously providing the advantages and new features of NFS. The announcement is essentially an end-of-life announcement for PAF and puts to rest rumors that PAF was dead already as well as rumors that FamilySearch would make one more release of PAF with New FamilySearch support.

> People seem to be doing okay with PAF's compatibility with Vista. The big > question is, how long will PAF, without being updated, continue to work > after Vista is superseded a couple of times? > > And as computers are replaced and new downloads of PAF are needed, will it > still be available even after it's no longer being updated and/or > supported? Don't worry about all of the what-ifs. They apply to all software. Some day, every program we currently use will cease to function on some new computer. That includes all of the other genealogy programs that are in existence today. Whether that is in 5 years, 10 years, or 30 years is irrelevant. When that day comes then we are forced to learn a new program, but our data will be able to migrate with us. Until then, the big question is "Am I happy with the program I am currently using?" If PAF does what you need, then there is no need to go through the pains of learning a new program. It is OK to just keep using PAF if you like it. Aloha, John

Gordon did not say PAF would no longer be supported. He also did not say that you had to stop using PAF. PAF, BY ITSELF, will not work directly with NFS but that is OK because FamilyInsight will act as the connection between PAF and NFS. And if you already have PAF Insight, FamilyInsight will be a regular update for you. No need to do anything special. When FamilyInsight is released, PAF Insight will notify you that there is an update and ask if you want to install it. FamilyInsight is one of the commercial programs that Gordon was referring to. So if you love PAF and want to keep using it, then go ahead and continue. Ohana Software has you covered. Aloha, John ----- Original Message ----- From: "Richard Halliday" <[email protected]> To: <[email protected]> Sent: Saturday, March 29, 2008 7:40 AM Subject: [PAF-5] PAF End-of-Life Announcement > All; > Yesterday I received the following from a friend. As a result I am > now looking at Legacy and Ancestral Quest. My tentative conclusion is > Ancestral Quest. Since it was the origin of PAF 4 & 5 it looks more > familiar, it appears to handle the source citations better, its date > modifiers (abt, bef, est, etc.) seem to be more familiar and it already > has at least a partial interface with new FamilySearch. > Comments? > Richard L. Halliday > West Linn, Oregon (where Winter Springs Right Back" {this > morning's Oregonian}) > "If the Lord wanted it done perfectly, > He would not let me help." > > "Also at the conference,it was announced that a group of developers has > created an extension to the PAF database file format allowing continued > use of PAF files with the new capabilities of NFS. Commercial programs > equipped with this extension will be able to support existing PAF files > while simultaneously providing the advantages and new features of NFS." > > Those "developers" are Gaylon Findlay (developer of Ancestral Quest) and > John Vilburn (developer of PAF Insight). Ancestral Quest 12 already > exploits some of the extensions when used in its "PAF mode". > > Gaylon made this presentation at the Developers Conference: > [Wed., March 12] 11:00 Gaylon Findlay > PAF SDK/ Sync (C++) > The basic layout of the PAF 5 database structure will be covered, along > with the basics of using the PAF 5 SDK provided by the Church. From this > base, we will discuss the recent changes engineered by Incline Software > and Ohana Software to allow syncing with the new FamilySearch Family > Tree. http://ce.byu.edu/cw/cwgeneal/familysearch > http://ce.byu.edu/cw/cwgeneal/familysearch/class_description.cfm > > "If you go here and scroll down to the schedule you will find links to > the presentations. The presentations are available in PowerPoint, PDF or > Adobe Connect. Adobe Connect gives you the screen capture with the audio > portion of the presentation. The next best thing to being there." > -Renee's Genealogy Blog : > http://devnet.familysearch.org/Members/clarkegj/march-3-2008-familysearch-developers-conference > > > --- Lesly Klippel <[email protected]: > > Subject: Future of PAF > > Here is an interesting item I found on the "Ancestry Insider" blog. > > Mike Benning > > ========================================== > > Gordon Clarke (Family History Department) read an official statement at > the FamilySearch Developers Conference today announcing future migration > paths available to users of the venerable PAF genealogy software. Once > New FamilySearch (NFS) is fully available, PAF users will have several > migration options available. Users can perform a one-time transfer of > their data to NFS, which like PAF, will be free. Or users can purchase a > commercial genealogy program, many of which are currently developing > support for NFS. Also at the conference, it was announced that a group > of developers has created an extension to the PAF database file format > allowing continued use of PAF files with the new capabilities of NFS. > Commercial programs equipped with this extension will be able to support > existing PAF files while simultaneously providing the advantages and new > features of NFS. > > The announcement is essentially an end-of-life announcement for PAF and > puts to rest rumors that PAF was dead already as well as rumors that > FamilySearch would make one more release of PAF with New FamilySearch > support. > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message

Bill, The new database has a person chosen in preferences, RIN # 1, my father. That's not the person who has been showing up in the primary position after the match/merge has been totally completed. But, surprise surprise. After I sent my request for help and took a 2 hour break to watch the NCAA finals I came back and started the process again. Guess what; the problem disappeared. Now after the match/merge is completed, the same person is in the primary position as was in that position before. Have the cyber gremlins done a # on me, or what? Thanks for the help. Dick ----- Original Message ----- From: "Bill Buchanan" <[email protected]> To: <[email protected]> Sent: Friday, March 28, 2008 11:21 PM Subject: Re: [PAF-5] Match & Merge-strange thing occurs > Dick, > > I am not sure if I understand. In a new database, there is no person with > the RIN chosen in the preferences to be shown in the Family and Pedigree > views. As you import people, someone will be given that RIN, and they will > be displayed. > > In my experience side-by-side tiling of two databases works best when both > are in the Individual List view, and both lists are sorted alphabetically. > I > don't know if that is what you are doing, but in this case the first > person > alphabetically will be displayed at the top of both lists, regardless of > the > RIN. > > Bill Buchanan > > > ----- Original Message ----- > From: "Dick Cazier" <[email protected]> > To: "PAF5 Users" <[email protected]> > Sent: Friday, March 28, 2008 8:43 PM > Subject: [PAF-5] Match & Merge-strange thing occurs > > >> Maybe someone can explain this to me; and if something's wrong, let me > know what and how to correct. >> >> I've created a new database that includes only people related to my >> mother > (shirt-tail relatives etc), and am exporting from a much larger database > in > small increments. >> >> I've tiled the 2 databases, vertically, so I can view them both at the > same time. Example, I have John Doe in the primary position in both. I > create a GEDCOM of John's ancestors from the large database and then > import > it into the smaller one (my mother's). Then match and merge in her > database. This goes well and all matches are successful. But when I > finish > the match/merge, a new person shows up in the primary position in database > where I've just completed the match/merge. It's always the same person, > and > one who was not included in the import. I think, in situations like this > before today, the primary person, in the database I've just imported into, > has always been the person that was there before (as in the example of > John > Doe). >> >> Can someone tell me what's going on, why and what I can do to correct >> this > happening? Thanks for your help. >> Dick Cazier >> Lakewood, CO >> >> ------------------------------- >> To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >> >> >> -- >> No virus found in this incoming message. >> Checked by AVG. >> Version: 7.5.519 / Virus Database: 269.22.1/1348 - Release Date: >> 3/28/2008 > 10:58 AM >> >> > > > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the > quotes in the subject and the body of the message >

Dick, I am not sure if I understand. In a new database, there is no person with the RIN chosen in the preferences to be shown in the Family and Pedigree views. As you import people, someone will be given that RIN, and they will be displayed. In my experience side-by-side tiling of two databases works best when both are in the Individual List view, and both lists are sorted alphabetically. I don't know if that is what you are doing, but in this case the first person alphabetically will be displayed at the top of both lists, regardless of the RIN. Bill Buchanan ----- Original Message ----- From: "Dick Cazier" <[email protected]> To: "PAF5 Users" <[email protected]> Sent: Friday, March 28, 2008 8:43 PM Subject: [PAF-5] Match & Merge-strange thing occurs > Maybe someone can explain this to me; and if something's wrong, let me know what and how to correct. > > I've created a new database that includes only people related to my mother (shirt-tail relatives etc), and am exporting from a much larger database in small increments. > > I've tiled the 2 databases, vertically, so I can view them both at the same time. Example, I have John Doe in the primary position in both. I create a GEDCOM of John's ancestors from the large database and then import it into the smaller one (my mother's). Then match and merge in her database. This goes well and all matches are successful. But when I finish the match/merge, a new person shows up in the primary position in database where I've just completed the match/merge. It's always the same person, and one who was not included in the import. I think, in situations like this before today, the primary person, in the database I've just imported into, has always been the person that was there before (as in the example of John Doe). > > Can someone tell me what's going on, why and what I can do to correct this happening? Thanks for your help. > Dick Cazier > Lakewood, CO > > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message > > > -- > No virus found in this incoming message. > Checked by AVG. > Version: 7.5.519 / Virus Database: 269.22.1/1348 - Release Date: 3/28/2008 10:58 AM > >