On 17/08/2015 07:45, Brian L. Lightfoot wrote: > Its late at night. My fingers are blurry and my eyes are tired. Anyhow, as I > tried to Add Media for a source detail, I started to type in the first 5 or > 6 letters of the file that I wanted and Legacy starts to display a list of > files that meet those filenames as typed so far. At this point I got > careless and instead of clicking on the correct name from the list of > possible matches, I just hit the Enter key .. With only the first 5 or 6 > characters entered as the filename. > > > > What I got was an error window but instead of saying "File not found" or "No > Match", Legacy tells me that the incomplete filename that I typed in was NOT > SUPPORTED. The detail info specifically said "This is an unsupported file > format." I knew that file as a plain vanilla JPEG image that opened in > several other applications so why was Legacy being so particular. > > > > That's when it occurred to me that I never bothered to click on the complete > possible filename match or completely type in the filename. Perhaps this is > the same condition that one or two other users have mentioned in their use. > Apparently the problem is User Error --- an incomplete or non-matching file > name. I was nowhere near the 260 character filepath limit so that was not an > issue with me but could have been with other users who did approach that > limit and the filename was truncated. And this shows that a truncated > filename will result in the error "Not Supported".
I discovered a long time ago that Legacy doesn't like it if you don't include the filename extension when trying to open a file. I use FreeClip a lot and often have, for example, the reference for a UK Census stored there for pasting into Legacy, eg RG9-2604-89-20. If I paste that into the filename box to pen that file Legacy will give me the "not supported" message. I have to select the full filename - RG9-2604-89-20.jpg - which will appear underneath. > > > Memo to all the Legacy code writers: there is such a thing as "File Not > Found" and that would serve as a much better error message than "No > Supported". > Agree with you, there. -- Jenny M Benson Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://support.legacyfamilytree.com Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
