Infragistics Home

Infragistics Forums

Infragistics community online discussions.
Welcome to Infragistics Forums Sign in | FAQ
in Search

double.NaN is exported wrong

Last post 07-29-2008 9:40 by [Infragistics] Mike Dour. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • 07-25-2008 7:51

    • protinus
    • Not Ranked
    • Joined on 11-30-2007
    • Points 40

    double.NaN is exported wrong

    Hi,

    I have a grid with a cell value of double.NaN, showing as "n. def" (german locale). Thats correct and works as expected.

    Now I export this grid to excel, and I would expect a result of  #NV (e.g. also shown when you add a formula =NV() ), showing that no value is defined for this cell of type double.

    But, it is exported and shown a value 2,69653970229347E+308, which is definitely wrong and misleading.

     Is there a workaround?

    P.S.

    I do not want to change the value to zero within CellExporting, as zero is misleading (one would think it is a valid value), and is definitely another value than NaN.

    Filed under:
    • Post Points: 20
  • 07-25-2008 10:06 In reply to

    Re: double.NaN is exported wrong

    I was unable to use the =NV() formula in Excel 2007. If you can post a workbook file with this error in one of the cells I might have a better understanding of how this error type works so I can offer more help.

    • Post Points: 20
  • 07-29-2008 3:55 In reply to

    • protinus
    • Not Ranked
    • Joined on 11-30-2007
    • Points 40

    Re: double.NaN is exported wrong

    file is attached:

    D2 .. D5  the expported value:

    2,6965E+308

     B8: The value that I would have expected (#nv)

     

    • Post Points: 20
  • 07-29-2008 9:40 In reply to

    Re: double.NaN is exported wrong

    It appears the function names might be localized and that is probably why I could not use the function. In the workbook you sent, the formula was =NA() and the error value was #N/A. However, while I agree with you that the value our Excel assembly is exporting is incorrect, I believe a divide by zero (#DIV/0!) error should be in the cell, not #NV. The reason for this is that Double.NaN occurs when you divide 0 by 0. If you place the formula =0/0 in a cell in Excel, it results in a #DIV/0! error.

    In either case, it is a bug and I would recommend submitting this to the support group: http://www.infragistics.com/gethelp.

    • Post Points: 5
Page 1 of 1 (4 items)
Powered by Community Server (Commercial Edition), by Telligent Systems