Our application has to support reports where each line on the report could have values which could be in different currencies.
To represent the currency format correctly we have been using the expression
'\' + currsymb + '#,##0 ;[RED](' + '\' + currsymb + '#,##0);
This works great when the currency symbol is a single character like $, however US$ as a symbol doesn't work. What happens is that the value in the column loses 2 digits of precision. (e.g $800,000 becomes US$8,000).
I suspect that we have to parse this out and provide an escape for each character when there is more than one. Supplying the '\' in the currsymb value doesn't appear to work.
This is the behavior in 12.6, and will confirm in 2017R2
Anyone have a solution for this, or is there a feature in 2017R2 that we can use going forward.
