Tony-

We do need the unique names; no, we have to have them. Suppose I had
the following:
1> BrownPhoto.jpg in C:\Photos  (This might be "Kathy.")
2> BrownPhoto.jpg in C:\Camera  (This might be "David.")
3> BrownPhoto.jpg in D:\Family  (This might be "William.")

Now I have everyone's photo linked correctly and it works. Then I
replace Kathy's photo.  Legacy will do its job and look for
"BrownPhoto.jpg." It will find it, but it won't be Kathy's photo. Had
I been using unique names, Legacy could probably find Kathy's photo
if it existed.

Robert


At 2010-05-02  06:14 PM, you 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


Reply via email to