And, don't you just love that you can clipboard an event and add it to anyone else? I like that so much more than sharing since you cannot change anything with a share without it affecting every other shared person on that event. Speaking of handy, I also LOVE being able to clipboard sources where I can make any changes I need to as I go on. (I'm in the process of adding a lot of sources to my folks)
Jane in Phoenix -----Original Message----- From: LegacyUserGroup <[email protected]> On Behalf Of Brian Kelly Sent: Monday, September 26, 2022 3:52 AM To: [email protected] Subject: Re: [LegacyUG] Importing a .paf file into a new LFT file Gene, What you are seeing is probably because PAF did not support the use of Sources. Because of that people would insert their source details into the notes preceding them with a special character (I think it was an Exclamation Point) Since notes may or may not contain source info and there could be multiple source entries in a note Legacy cannot extract and create sources from those note entries. I do not think there is any way except to bite-the-bullet and manually create a source from those PAF note entries. You can create a search list from those using each census event and work through it until you have created sources for each one. Slow but sure will win the race. I have been working since June in my file and have successfully worked through to add 1911 and 1901 Census events from the Canadian Archives. I finished the 1911 census and started the 1901 census on 17 Aug there were 706 starting people in the 1901 list and yesterday I had the count down to 390. Brian Kelly On 25-Sep.-22 9:01 p.m., Gene Wheeler wrote: > Is anyone familiar with importing an old .paf file into a new Legacy file? > > I know it can be done directly from *.paf into Legacy, but I am > experiencing a problem that needs to be fixed. It has to do with > importing census events. During the import, census events are created > as such; however the census data itself is placed in the General > Notes, rather than within the census event. Thus, when creating a > descendant report, the information is not presented as it should be. > > There are simply too many of these to try to cut 'n paste or drag 'n > drop. I would hope there is some way in the import setup to make sure > the data is placed within the census event. > > Thanks for any suggestions! > Gene > -- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/ -- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
