Thanks , – but what I'm saying is that the problem still occurs in 5.4. We have reproduced it.
When I had my call with Quest, of my three cases, one was reported fixed in 5.4, and that was the end of that one. Quest opened a bug on the other two (including this one) because it is not fixed in 5.4.