Hi Agnes,

I'm not sure why do you expect any query to fix your bad data. The fact that you don't know exactly what result you want doesn't help either.

>I agree with this. OTOH I have cases where I tend to live with the wrong result. I have some stuff that is not 100% normalized. Lets say a unit is used. This is a information that is nothing then nice, it has no influence into any process. This is plain text and used over and over. Normally it comes as import so all is fine. Sometimes the user enters code via UI so he uses pcs, Pcs, Pieces, t, ton, Tons. Normally he does not mix up tons with pieces, so there is no real problem. In the old syntax, I just ignore the field and it gives a text. It might not be 100% accurate but good enough. (everybody how deals with the system knows the correct units anyway) So now it spreads me the summation into a couple of records. This is very unexpected. Ok I could do min or max or some other aggregate on unit but this again raises the chance of wrong results for mixed pieces and tons.
>
>So I'm not really happy.
>