Forum Discussion
From documents, I believe Decimal values can exist between +79,228,162,514,264,337,593,543,950,335 and -79,228,162,514,264,337,593,543,950,335. If your number falls outside this range, at any point in the calculation, you'll get that error. You can probably break that range even if the number is technically inside the range but having a large amount of decimals.
- CAIGuySeanF2 years agoContributor
I assumed it could be range driven, but in the example above, I don't ever come close to falling outside this range?
- DanielWillis2 years agoValued Contributor
I think like Jack hinted, it is the amount/size of numbers after the decimal place (i'm sure there is a better term for that.. precision?).
CellAmount accepts a decimal so falls over when you try to send the value there.
I wonder if you could (if its acceptable) store the value in a double and then round it and send it to CellAmount?
So
Dim DoubleCellAmount = CAGRCalc.Cellamount ^ ExponCAGR - 1
CAGRCalc.CellAmount = Math.Round(DoubleCellAmount,X)
where X is some value that is acceptable to you
- Henning2 years agoValued Contributor II
Hi, did you try converting your decimal to a string and logging this in the error log to see what might be the issue here?
- CAIGuySeanF2 years agoContributor
excuse the ignorance on my part, but not sure how to do that?
Related Content
- 12 months ago
- 8 months ago
- 3 years ago
- 6 months ago