It could well be the same problem as the merge in all the 20008 plus versions would rely on the same Ancestry merge code?
So with a bit of luck the fix, whatever it is at the Ancestry.com end, should address the issue in all versions, which may be one of the reasons why Ancestry.com jumped on it so quickly?
John D
So with a bit of luck the fix, whatever it is at the Ancestry.com end, should address the issue in all versions, which may be one of the reasons why Ancestry.com jumped on it so quickly?
John D