Just tried the new facility. Are the the FAMC and FAMS records missing from the gedcom file?
Can someone else try an export and verify this?

Ian

Yes
Many/Most programs ignore these on import.
Are the missing FAMC and FAMS causing a problem?
--BC

This may seem silly but when I try to download the GED file nothing really happens. I get a screen with a webpage filled with data that looks like it could be a ged file but no way of saving it or exporting it anywhere. When I try to save it to my computer via the file "save" after "select all" function my Legacy program does not recognize the file as a GEDCOM file. Is there something I am missing here?

I'm not familiar with the "select all, then save" method..
My browser/OS gives me a choice to either "open" or "save to disk" when I click on the link.

Have you tried right-clicking on the link and selecting "Save Target As" (Windows & Internet Explorer) or right-clicking and selecting "Save Link As" (Windows & Firefox)?

Thank You!! The right click was the trick. Now the file is recognized as a GEDCOM and I've successfully entered it into my Legacy program. Many thanks.

Yes I get the same thing. I'm trying to import my Ancestry gedcom into 'phpgedview' and 'The Next Generation' to display my tree on a website. When importing this file with phpgedview, I get 250 individuals but no relationships, with TNG I get just the source details but no individuals being imported.

Forum posts for both of these programs say it's a problem with Ancestry.

I had the same problem until I figured out that just adding a spouse doesnt add a MARRIAGE relationship! I sent a feedback and made a post about it here:
http://boards.ancestry.com/topics.ancestry.ancsite/9032/mb.a...

I didn't realize what you two 'gedcom geeks' :-) were talking about until recently! I sent feedback and made a couple of posts about this just now.

How could 'many/most programs ignore' family information!?
This is a major p.i.a. (and bug imo) when importing a gedcom & all of your spouse linkages are lost!!

The FAMC/FAMS pointer are redundant with the info in FAM groups and therefore many programs including FTM and Ancestry Member Trees’s own GEDCOM import get all the family information from FAM group and thus ignore the redundant FAMC/FAMS pointers without loosing any family information.
Although the GEDCOM works fine in most cases, some programs must rely on the FAMC/FAMS pointers thus causing the problems mentioned.
Therefore we acknowledge this as issue that needs to be fixed to properly output the FAMC/FAMS pointers.
For now the workaround is to import into PAF or FTM, then export again to new file and re-import into your application.

Sorry for the inconvenience…
--Bennett

Who are you, Bennett? If you are "official", please identify yourself as such.