I have some concerns about merge and there are some problems with ShareMerge creating additional citations etc.
I have been bringing together many small databases in expectation of Dynamic Groups being introduced in the not too distant future and have been surprised with the number of duplicate persons after running the automerges. I exported a sample to look at the _UID of each person expecting RM to be to blame but the _UID's were all different. Thinking about my past practices I then realised that when I dragged and dropped John Doe, selected "Everyone in the same Tree", and confirmed that John Doe was the same person I was dropping onto, then John Doe maintained the same _UID but everyone else in his tree got a new _UID. That is currently my suspicion and I believe it will prove to be true.
When you stated the "exactly the same ID" were you referring to the _UID in the gedcom file or Ref No?, if you are not sure export the two individuals in question and open the gedcom file in Notepad as a text file, at the start of each person you will see a line like "1 _UID 94701BD8919CF543A5A1DFCE4000686E65BC", that it the Unique Person ID and if they are both the same I believe RM will merge regardless of other facts.
Yes I mean the UID number that Rootsmagic gives every person in the database, not any user generated reference. The number that shows next to the persons name in manual duplicate merge. If 2 people have the same RM number you cant merge them into 1 because ts the same person
Also , backups take just under a minute in RM4 even with 1,700,000 people, but it takes about 30mins-1hr to backup the same size gedcom in RM3. It takes a few hours to import the gedcom into either RM3 or RM4
Its just the manual merge , where you merge 2 people which is excruciatingly slow ie 30 mins per person, when you click to go back to the main list of people. I havent tried the automatic duplicate merge search as going by the manual merge it will take hours &/or it will crash & I dont want to corrupt this large gedcom
Try importing these gedcoms into a database, then try manually merging them in RM4, that will give some idea of our problem
This will make a comparable large gedcom for testing