Cathy, Thanks for your reply, but I still think the bug is a significant one that should be fixed as soon as possible.
The bug affects Search & Replace changes to both newly-created Master Sources and those created from an existing Master Source. MS Access can be used to make the changes properly, but you have to do it in both the "SrcName" and "Contents" fields in Table "tblSR" of the fdb database. It appears the S&R changes made directly in the Legacy program now only modify the "SrcName" field, as shown below in excepts from Table "tblSR" after making changes to two sources in Legacy with S&R: >From "SrcName": 4001 - Created as New Source - rev. in S&R 4000 - Created from Existing Source - rev. in S&R >From "Contents": [Master Source List Name]|4001 - Created as New Source|[Title]|US City... [Master Source List Name]|4000 - Created from Existing Source|[Title]|US City... The bug fix appears to simply have Legacy also modify the "Contents" field for the S&R changes. FYI, this only applies to sources created by SourceWriter and not Basis Style sources, which do not have any entries in the "Contents" field. Hope this helps your programmers Donald Quigley Escondido, CA Quigley Doyle Family Tree -----Original Message----- From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Cathy Pinner Sent: Friday, February 26, 2016 9:42 PM To: Mailing List for users of Legacy Family Tree software <[email protected]> Subject: Re: [LegacyUG] Changing Source List Name Don, We never know when a bug will be fixed. This bug really only affects you when you create a new Master Source from an existing Master Source. I know as I have it in my Master Source list. When the bug is fixed, you can probably do another Search and Replace to fix them? The alternative is to do it in MS Access. I won't tell you how and where as if you can't find it for yourself, you shouldn't be doing it. Cathy Don Quigley wrote: > Brian, > > Any idea when the next revision to Legacy comes out& hopefully will fix this bug? I'd like to do a lot of S&R to clean up and "standardize" my Source List Names, but can't do so until the bug is fixed. > > Donald Quigley > Escondido, CA > Quigley Doyle Family Tree > > -----Original Message----- > From: Brian/Support [mailto:[email protected]] > Sent: Friday, February 12, 2016 5:34 AM > To: [email protected] > Subject: Re: [LegacyUG] Changing Source List Name > > The problem report for this has been submitted. You are right, it only applies to SourceWriter style sources. > > Brian > Customer Support > Millennia Corporation > [email protected] > http://www.LegacyFamilyTree.com > > On 11/02/2016 17:10, Brian/Support wrote: >> This appears to be a bug. You are correct the change seems to take >> place in the Master Source List but when edited the old name still shows. >> >> Our bug reporting system is down right now but I have flagged this >> message and I will submit a report when the system comes back up. >> >> Brian >> Customer Support >> Millennia Corporation >> [email protected] >> http://www.LegacyFamilyTree.com >> >> On 11/02/2016 16:37, Don Quigley wrote: >>> Has anyone else had the problem of getting Source List Names changed >>> by Search& Replace? >>> >>> After a change in S&R, the source name appears as having been >>> changed in the Master Source List, but when the Edit box is opened, >>> the old name is still there. If I then hit save instead of cancel, >>> it goes back to the old name in the Master Source List. >>> >>> Very frustrating when I have changes to be made to 4000 source names! >>> >>> Donald Quigley >>> Escondido, CA >>> Quigley Doyle Family Tree<http://www.donquigley.net/> >> -- _______________________________________________ LegacyUserGroup mailing list [email protected] to manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com -- _______________________________________________ LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com
