GEDCOM import from ancestry.com

I am trying to import a GEDCOM from ancestry.com. The result is that all the profiles show up double in Aldfaer in an empty tree. I have tried with and without notations with no effect. I read the article about importing GEDCOMs from MyHeritage and assume that this problem is similar. However, I am at a loss about what to try next.

If you mark 'Add to current database' all data will be added to existing familytree.
You have to import it into an empty tree.

Daniel,
you may send me the gedcom and I'll see what I can do.
Click the 'Meer' button and mouse over the envelope to see my mailaddress.

That's exactly what I did Rene.

The gedcom file which I received contains a construction around the importing of objects which is not supported bij Aldfaer. Reference 0 @O4789@ OBJE

Trying to import the gedcom results in a message and an empty *.ald ifle.

I have checked the file thr a Gedcom validator and find some 32085 issues.

This is very disappointing because it means that Aldfaer is of no use to me. Is there some kind of work around?

Your gedcom construction around the OBJECT uses also the tag FILE. Your detail of the FILE tag fails to have a proper path and filename.
OBJECTS within the FAM segment are not supported at the moment.
There is no way around unless you submit a gedcom without images and the like.

Han, Daniel
Could it be that Ancestry already uses Gedcom version 7?
If so, do they offer the choise to use 5.5.1 ?

I am online with the helpdesk at ancestry. They claim to be using "standard GEDCOM format:. I will check if there is a choice of versions. So I gather that you are saying that Aldfaer uses version 5.5.1.

The gedcom I received is a 5.5.1 version as stated also by the validator of Chronoplex Software.
However, there are many issues, so it could be manipulated.

It failes because of wrong specification of de FILE tag within the OBJ construction.

I just retried exporting a GEDCOM from ancestry. There is no indication of which version they are using and also no option for choosing one.

At least we now know which version they are using. However, with nearly 7000 people in the tree I have no desire to change all the lines by hand even if I did know what the form should be. This is enormously frustrating. One should not have to be a computer scientist to use this software.