Mike,
I am using Infragistics v10.1. In my grid i am using formula to show the round off value. I used "Roundup" in the formula. Every thing is working fine except some value.
For example for the value "17593512.76" it gives "17593512.77", "17593512.67" it give "17593512.68", "17593512.85" it gives "17593512.86" and for "17593512.94" it give "17593512.95".
But it is showing the same value in excel.
Is there any logic in round up?
For you reference i attached a sample application with this post.
Steps to reproduce :
a) Run the application
b) Enter value "17593512.76", or "17593512.67", or "17593512.85" or "17593512.94" in the column "Payment"
c) Check the value in column "unboundcolumn1"
Guide me to solve this issue.
Hai Jose,
The roundup issue solved in the service release "WinForms_11.2.20112.2004".
Thanks for your support.
Hello,
Rounding up issue has been addressed in service release versions:WinForms_10.3.20103.2140 WinForms_11.1.20111.2050 WinForms_11.2.20112.2004
This service release is now available under your account at the Infragistics Website. To download the service release, log in to ‘My IG’ and select ‘Keys & Downloads’. Select the appropriate tab for this product; then the license key. The available service releases (Hot Fixes) should now be listed on the page.
If you have any questions regarding this matter please don't hesitate to let me know.
I will be happy to help you out with this issue.
I have created a case for you to better assist you with this issue going forward. To access the case, simply log into your IG account and click on My Support Activity.
Please let me know if you have further questions in this matter utilizing the case created.
Hi Suresh,
I took a look and I get the same results. This seems like a bug to me.
It has something to do with the imprecise nature of the Double data type, which is what the CalcManager uses for all calculations.
I will forward this over to Infragistics Developer Support so they can create a case for you and write this up for developer review.
Of course, v10.1 of NetAdvantage is retired, so any fix for this issue will only be available in the latest versions.
Hai,
Anyone have solution for above mentioned problem?