What is "significant impact"? --> Lets come back on the Merge objects In the vast majority of case, a reference to a repository object is a repository link. If an object 01 (source) is merged with an object (2), the user can choose to transfer the links targetting O1 to O2 In certains cases, reference to a repository object is stored in a binary property. This is the case for example of a diagram drawing. The position (x,y) of an object in the drawing is store in the property '_Drawing' of the diagram. If O1 is merged with O2, it would be too time consuming to analyse all the diagram drawings of the repository and chnage the reference. That is why merge objects exist. Technically speaking a merge object is a data that a tool managing binary property storing object references (such as the diagram editor) can consult to avoid a small inconsistency.
To be short, the only significant feature I can think are diagran editor and text editor (field and rtf format) Example: O1 is merged with O2 A _transferred object T1 is created. T1 is deleted.
Impact on diagrams previously displaying O1 Position is lost: O2 is displayed in the top left corner of the diagram. If T1 has not been deleted, the drawing would display O2 with the previous position of O1 Texts/comments previously quoting O1 using MEGA fields Susbitution is lost: The field displays the name O1. If T1 has not been deleted, the field would displays the name O2.
Why only half of the objects are deleted at each run of the script of KB 00000257 --> Script of KB 00000257 works but several loops are required for technical reasons. Code deleting of objects should be written differenlty to avoid this.
You can use a while loop
MsgBox "There are " & ListToDelete.Count & " _TransferredObject."
Do while ListToDelete.Count >0
MsgBox "Deletion has ended. There are " & ListToDelete.Count & " _TransferredObjects."