You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Incorrect Sum reporting at the bottom of Browse Data tab status bar #4033
When selecting values across multiple rows in Browse Data tab, the bottom of the screen display a stratus of number of rows and columns selected, and basic statistics such as Sum, Average, Min, Max. However, on multiple occasions, the value for the Sum is incorrect (off by a few cents). It should display correct Sum or just not display anything at all.
What did you expect to see?
A correct sum or some kind of indication that the value is approximate and not accurate.
This seems odd .. and something no one else has reported as yet.
Have you a screenshot, or better yet, a database exhibiting this behaviour? (any sensitive data can be erased .. its just the figures that are important).
I assume the fields are the REAL data type? Are they static values or calculated?
For example, its common in calculated REAL fields for their to be discrepancies - accounting have had this for years in VAT calculations, for example. Its worse when compounded, so for example, a bad system would calculate vat amounts from net, then totals by adding this calculated value together. If the vat amount was 3.455 it would round it up to 3.46, then this would create a total a penny out. If an invoice consisted of 100 items, this could cause wider discrepancies.
Activity
chrisjlocke commentedon Oct 11, 2025
This seems odd .. and something no one else has reported as yet.
Have you a screenshot, or better yet, a database exhibiting this behaviour? (any sensitive data can be erased .. its just the figures that are important).
I assume the fields are the REAL data type? Are they static values or calculated?
For example, its common in calculated REAL fields for their to be discrepancies - accounting have had this for years in VAT calculations, for example. Its worse when compounded, so for example, a bad system would calculate vat amounts from net, then totals by adding this calculated value together. If the vat amount was 3.455 it would round it up to 3.46, then this would create a total a penny out. If an invoice consisted of 100 items, this could cause wider discrepancies.
chrisjlocke commentedon Oct 15, 2025
cough