Lee Hoffman wrote, in part: > Hmm! I vaguely remember discussions about including > multimedia files in a GEDCOM and later GEDCOM version > specs (not sure of the earlier versions) speak to having > the file in the GEDCOM in "encoded multimedia lines". Lee, GEDCOM v5.5 has a BLOB (binary large object) record that was intended to be used to include images and other document content inside a GEDCOM file. It was dropped in v5.5.1. Very few programs support BLOB, and at least two of the programs that support it (Family Historian 6 and Ancestral Quest 14) are incompatible: Ancestral Quest 14 cannot read BLOBs from FH 6. That's not surprising; there is at least one error and one ambiguity in the specification of the format. GEDCOM v5.5.1 is the de facto standard and (IMO) GEDCOM files should not include BLOBs. TMG says that it writes GEDCOM v5.5 and v4.0. As far as I can tell, TMG does not write BLOBs. Here's an article about v5.5.1 vs. v5.5 and earlier versions of GEDCOM: http://genealogytools.com/why-all-genealogy-apps-should-support-gedcom-5-5-1 / GEDCOM v5.5 and v5.5.1 support "links" to external files. For example, here's how TMG writes GEDCOM records for an exhibit: 2 OBJE 3 FORM PNG 3 TITL Graham, Isaac 1868 death 3 FILE c:\Exhibits\1868-07-22-Graham,Isaac-101-death.png The problem with this approach is mostly that moving the GEDCOM file to a new machine will usually invalidate the file path, and that means editing the GEDCOM file or using a facility in the importing program to designate where the exhibit files reside on the new machine. John