Hi Geoff, Ken & others, Geoff wrote: >The entire Legacy's Ultimate Guide to Sources CD is devoted to teaching >about sources. An upcoming CD will teach methodologies, principles, and >data entry guidelines for census records, city directories, pension >records, and much more.
The posting about Legacy and Sources made me wonder what the status of the Merge/Source/Bug/Feature was? There was a number of posts about the issue but it has not been listed under the usual list of fixed items these last few months. >I like the idea of a source tab also, it would be a nice feature. >It's been added to our list of things to work on. >Thanks >Ken McGinnis > >From: "Cal Matthews" <[EMAIL PROTECTED]> <To: <[EMAIL PROTECTED]> >Sent: Tuesday, July 16, 2002 6:29 PM >Subject: Re: [LegacyUG] Merge/source/corruption bug > I agree Ken. re: Fixes > > Controlling ALL the sources attached to specific event items in the > data is very important, especially during a merge. > > ----- Original Message ----- > From: "Ken McGinnis" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, July 16, 2002 5:31 PM > Subject: Re: [LegacyUG] Merge/source/corruption bug > > | Fixes: > | ================ > | I can add a new option to save a few keystrokes. My proposed change > | is to add another menu item to the Options button on the bottom of > | the merge screen that would read something like "Don't combine sources > | for unselected| information". > >From: Barry Kruger >Subject: [LegacyUG] Merge/source/corruption bug >Date: Mon, 08 Jul 2002 04:27:46 -0700 >Hi, > >I downloaded the latest update to my Legacy 4.0 Deluxe and >the merge/source/corruption bug is still there. > >Others have confirmed the problem as well (Steve Addison). > >Regards >Barry > >From: "Steve Addison" <[EMAIL PROTECTED]> >Subject: [LegacyUG] Sources incorrect on merging >Date: Sat, 15 Jun 2002 23:41:55 +0100 >Reply-To: [EMAIL PROTECTED] > >Whilst doing a bit of merging this evening it has become >apparent that Legacy is not handling the sources correctly >when merging takes place. For instance, if two pieces of >data are different and with different sources, say birth >data, if you just ignore the incoming data and keep your own, >Legacy still assigns the incoming source to your own data, >thereby corrupting the sources by adding a source to your >own data which is incorrect and not for that data. > -----Original Message----- > From: Barry Kruger [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 21, 2002 12:27 PM > To: LegacyUserGroup > Subject: Sources incorrect on merging > Hi Ken, > > >----- Original Message ----- > >From: "Ken McGinnis" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Thursday, June 20, 2002 2:44 AM > >Subject: Re: [LegacyUG] Sources incorrect on merging > > > > This source issue is definitely not a family file issue. It is easy to > reproduce this problem in any file. Create two new individuals. Give one > a birth date with no source. Give the other a birth date source but do not > enter a birth date. Merge them. Now watch as the source has > jumped to the birth date and now has suddenly become the source for > the date to which it was never attached or intended. > > Regards > Barry Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
