At 11/18/2017 17:57, John Cardinal wrote >I am not an expert on exporting GEDCOMs from TMG, but my experience is that >they take a long time. To make sure I wasn't misremembering, I just did a >test and exported my 27,000 member project and it took 20 minutes. In my >opinion, that's slow. Backing up my project is much faster, no more than a >minute. I have never noted a GEDCOM export to take more than a few minutes. However, I have never exported a GEDCOM with more than a few thousand persons. I have noted that TMG takes longer to export a GEDCOM as the number of person increased. Also an export of a subset of a data set will also increase the length of time. A recent export of a 5000 person subset took quite a long time (15 - 20 minutes?). Having TMG create a new project of that same subset and then exporting a GEDCOM from the new project took a total of about 8 minutes. >I did include exhibits in the GEDCOM file. I don't think TMG will include >internal image exhibits (I don't have any), but it did include external >image exhibits (GEDCOM 5.5 supports that) and it also exported internal text >exhibits. The external image exhibits should not slow TMG down. It doesn't >copy the image files, it writes the path to the file in the GEDCOM file. 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". Thus the file would be encoded and fully included in the GEDCOM file. My vague recollection of that time is that such encoding had a lot of problems. Including File Paths would get around that problem assuming that the exported GEDCOM was to be imported on the same computer. Otherwise, I would think there would be a lot of work required to prepare the GEDCOM for import on another computer. Lee