Hi,
Having problems with DSUM-functions. I'm successfuly using the function in a big template to calculate the differences between the sum bought and sold units of certain products, with data from two different (uncompatible) systems.
The function used is the same in all cells (250 rows * 30 columns). The criterias are of course different, fetched from another sheet. The DSUM function is summarizing all the user names in the rows above itself, and then removing them again by using the normal SUM, leaving the sold / purchased sum of product quantity for an employee.
=DSUM('database1'!$A:$BD;"Product Qty";'db criterias'!$AG$1:$AH203)-sum($I$2:$I202)
where the criterias in 'db criterias' are a buch of usernames.
Its working like a dream - but for one cell... when using the 'evaluate function' tool, everything works out fine until the last (final) moment, when it's calculating "684-684" and somehow ends up with -210...
Have reported the problem to Microsoft, no answer yet. Has someone else experienced something like this? Or even better, knows how to solve (or avoid, by all means) the problem?
Thanks
Having problems with DSUM-functions. I'm successfuly using the function in a big template to calculate the differences between the sum bought and sold units of certain products, with data from two different (uncompatible) systems.
The function used is the same in all cells (250 rows * 30 columns). The criterias are of course different, fetched from another sheet. The DSUM function is summarizing all the user names in the rows above itself, and then removing them again by using the normal SUM, leaving the sold / purchased sum of product quantity for an employee.
=DSUM('database1'!$A:$BD;"Product Qty";'db criterias'!$AG$1:$AH203)-sum($I$2:$I202)
where the criterias in 'db criterias' are a buch of usernames.
Its working like a dream - but for one cell... when using the 'evaluate function' tool, everything works out fine until the last (final) moment, when it's calculating "684-684" and somehow ends up with -210...
Have reported the problem to Microsoft, no answer yet. Has someone else experienced something like this? Or even better, knows how to solve (or avoid, by all means) the problem?
Thanks