Brian, is this the same problem? In the problem that we are talking about, a link IS created; it's just that nothing is distinguishing the pictures from the other types of multimedia -- they are all imported as if pictures. (Maybe the problem report that you found was half fixed?)
I don't know whether this idea of treating pictures differently from other files is unique to Legacy, in terms of how they can be opened/viewed within the program. My guess is that FTM must treat them all the same, or else its export would somehow differentiate them. Even if this is an FTM failing, perhaps Legacy could recognize the filename extension in the GEDCOM and take the appropriate action on import. Ward -----Original Message----- From: Brian/Support Sent: Thursday, May 02, 2013 8:13 AM To: [email protected] Subject: Re: [LegacyUG] GEDCOM 5.5 Import problems with media file links We do have a problem report in our system for this issue of importing multimedia links from FTM 2012. The issue is still shown as outstanding. According to the problem report FTM 2012 uses a custom GEDCOM Tag to identify the link to the media when linking it to people. Legacy does not recognize this custom tag so it, naturally, does not know what to do with it so the multimedia link is not created. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com -- On 01-May-13 22:34, Ward Walker wrote: > I had the same problem, which I repaired manually. One way to find them > is to look at the GEDCOM file in a text editor like Notepad. If you > scroll down near the bottom, you will see a bunch of FILE records. Look > for the ones with .pdf file extensions (or other non-pictures, such as > .htm or .doc). For each one, copy the object link, such as @M115@. Paste > that into the Find string (use ctrl+F or use the menus) and search > upward to find where the object was referenced. Then from there, scroll > up carefully until you see the first 0 record, which is usually followed > by the individual’s name. > This is one of several serious issues I had with FTM exports. I logged > some requests with Legacy for workarounds, even though it is not > Legacy’s fault. I don’t think I logged this one, although a > workaround > could be imagined for the Legacy import. Maybe more people should log > enhancement requests related to FTM-to-Legacy transfers. > Ward 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 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
