Mary Grindol wrote: > I have a fairly large database and export to GEDCOM quite often - > to share with Ancestry.com, RootsWeb.com, and MyHeritage.com. I > have NEVER had an export take 45 minutes. I wonder if Chris, or > whoever said this in the first place, was trying to export exhibits > (which aren't recognized by GEDCOM anyway). No one else seemed be > shocked at 45 minutes, but I am. I don't think my GEDCOM reports > take much longer than saving to a backup (since I also don't backup > the exhibits because they are external). Mary, 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 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. I have a little experience with importing GEDCOM into TMG, and that is really slow, though there are wide variations based on the characteristics of the GEDCOM file. The other day I imported a 140,000 person GEDCOM file and it took more than 24 hours. That file was exported from Reunion for the Mac and there were various issues with it. I wrote a program to adjust the Reunion GEDCOM file and make it more standard. When I imported the modified GEDCOM into TMG, it took about 3 hours. John