Bug in the "Remove" of virtual copies

@Joanna Typically Win10 automatically changes the copy numbers automatically and if you watch closely you can sometimes see the [2] change to [1] except on the few occasions where it has remained at one.

The reason for the size and depth of the test, raising “manhole” covers and monitoring the database etc. was to see what was going on and the truth is that there are no VC numbers that I can see in the database.

It is all done by “sleight of hand”, i.e. it is a display issue and is controlled by the position of data in the database and the associated location of data in the DOP! If there were VC numbers in the database then every time one VC was deleted the remaining entries would need to be “fixed”, instead it “only” requires an adjustment of the display only!

How different the code is between the DxPL(MAC) and DxPL(WIN) I do not know and it does not occur that frequently but frequently for me to have captured a snapshot on two occasions!