I appreciate the reply @GeorgiaC but we're not asking for an ENHANCEMENT - we're asking for a clear & obvious bug to be rectified.
We discussed this at length last year & early this year too I think. This is a bug that has been caused by bad coding (as above, the coders will know where because it's happened several times before). This is a bug that's been allowed to go into production due to an abject lack of quality control.
There is a perfectly apt post in the Idea Exchange Forum - Sometimes you just need to leave it alone!!
It was quickly closed!
Tells you everything, I think.
