Tony, Now you tell me. I too use simple filenames (such as pagexyz.jpg or mary.jpg) in a complex tree of subdirectorys. I have long known better than to push a button that says "Do you want Lecacy to search for the file?" However, The button Options > Customize > Locations > "Test All Multimedia Locations" has always seemed safe to use. The next window says Check all Picture, Sound, Video and Document files to make sure they can be found in the locations specified. You will be prompted for a location for all files that cannot be found. For 5 years I've been finding an occassional wrong picture attached to an event. I've always thought I must have linked it incorrectly. Only recently I discovered that Test All Multimedia Locations button was only reporting files that couldn't be found in any Legacy directory. but if it could not find a German baptismal record named page123.jpg it will reroute it to a french marriage record named page123.jpg. Also the part about prompting for a location for all files that cannot be found is false. I reported this as a bug only a week or so ago and have not received a reply. I can't believe Legacy could tell you it is working properly. That button is unsafe to use yet I need to check a 2nd computer that is not up to date with files recently added or changed on my main Legacy computer.
-- Richard Van Wasshnova http://www.gencircles.com/users/vanwasshnova http://gw.geneanet.org/vanwasshnova On Sun, May 2, 2010 at 4:14 PM, Tony Rolfe <[email protected]> wrote: > A few weeks ago I reported what I thought was a bug but, after a few > e-mails, the developers have told me that Legacy is acting as designed and > they won't be changing things. I thought it would be a good idea to mention > the problem here, so everyone is aware. I know it happens in this > particular situation and suspect it happens in other similar areas as well. > > Imagine you have an individual with an event, the event has a source and > the source detail has an image attached. Now, if you move the image into > another directory, nothing happens until you use Legacy and highlight the > source. At this point, Legacy realises that the file isn't where it was, so > it goes off and looks in all its known directories, finds it for you and the > file is magically relinked. You might never know this has happened. > > That's all well and good, except that Legacy isn't actually looking for > that file; it is looking for a file of that name. If there is a second file > with the same name anywhere in Legacy's known directories, then Legacy is > just as likely to find the other one and relink that. Without telling you. > > Of course, if Legacy can't find any file with that name, it comes up with > the familiar requester and, if you let Legacy search for you, it will ask if > it finds the right one. > > I was hoping that the "Is this the right file?" would be inserted when > legacy finds one in the scenario above, but apparently that isn't going to > happen, so I guess the advice is to make sure that all your files have > unique names. > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
