Hi John and Chris, I agree that TMG is slow at many things. Backing up a TMG project is the equivalent of zipping up the equivalent 90 files. That is the time to compare for that case. When do some other work with WireShark to analyze efficiency of programs I was amazed at the overheads at the system level when opening and closing the various files. Collating data within TMG to go into a GEDCOM requires a lot of dancing from table to table (file to file), so it is quite likely that exporting a GEDCOM from Family Historian where all its data is said to be in memory and it is GEDCOM structured is likely to represent a minimum exporting time. TMG's architecture was probably reasonable in 1995, but it is not competitive with applications built 20 years later. There is no way to fix it within TMG. It is for this reason that HRE will probably do a behind the scenes 2 stage TMG to HRE migration process. We already have software that will clone the ~90 file TMG VFP  Project to a single file H2 TMG ghost Project. Once we are dealing entirely with the H2 database we can build an extended schema, ghost TMG and partly preloaded HRE schema table in the same database. Then migrate TMG data to its home in the HRE schema tables. At the end of the process we then delete the ghosted TMG tables and now have an HRE Project copy of that TMG project. Hopefully, this strategy will make the migration quite fast (but subject some checks and balances about where certain customized TMG data should live in HRE). Robin On 19-Nov-17 09:27 AM, John Cardinal wrote: > 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 > > The TMG archive is found here: http://archiver.rootsweb.ancestry.com/th/index/TMG/ > Instructions on how to subscribe to TMG: http://lists.rootsweb.ancestry.com/index/other/Software/TMG.html > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message > -- Robin Lamacraft, Adelaide, Australia