Hi everyone, One of our users (a very high-ranking one, so denial was not an option [;)]) wanted to have a certain report sorted by a Decimal field of the underlying table. So I created the appropriate key and ran the report using this key. It started printing the first few entries and then repeated the same block of entries (5 or so) over and over again. I tried sorting the table’s overview form and another, “card-type”, report by the new key: No problem. Then I found out that the error was caused by the Decimal field in question also being used as a total field in the footer of the erroneous report. When I removed the total field, sorting by the new key worked fine. I then resorted to calculating the field totals in C/AL code using a total variable. It seems that fields being used as total fields can not also be used for sorting. Is this a mere bug or some technical limitation? And does this only occur with Decimal fields or also with Integers? It’s also a bit strange that there was no crash or error message, but instead an endless stream of the same group of records.