TrueDBGrid exports wrong numeric values to Excel output file

Posted by: mtashildar on 8 April 2020, 3:31 am EST

    • Post Options:
    • Link

    Posted 8 April 2020, 3:31 am EST

    TrueDBGrid exports wrong numeric values to Excel output file.

    .

    I have tried with C1TrueDBGrid.ExportTo and C1TrueDBGrid.ExportToExcel methods

    When the grid has numeric value of length above 15 then it will round off the value.

    For example if the value in a column is 1073810510006526 then exported value will be rounds off to 1073810510006530.

    And if the value in a column is 1073810510006523 then exported value will be rounds off to 1073810510006520

    Is it a bug?

    Regards

    Mahesh

  • Posted 8 April 2020, 7:49 pm EST

    Hi Mahesh,

    It is a known issue which is already escalated to the developers.

    For a time being, you can use the SaveExcel method of TrueDBGrid to get the correct values while exporting to excel.

    https://www.grapecity.com/componentone/docs/win/online-truedbgrid/C1.Win.C1TrueDBGrid.Excel.4.5.2~C1.Win.C1TrueDBGrid.Excel.Extensions~SaveExcel.html?highlight=saveexcel%2C

    Regards,

    Prabhat Sharma.

  • Posted 8 April 2020, 9:36 pm EST

    When this known issue is expected to be resolved?

    Since when it is known?

    Regards

    Mahesh

  • Posted 12 April 2020, 10:56 pm EST

    Hi Mahesh,

    We are getting in touch with the developers for the updates and will let you know soon.

    Regards,

    Prabhat Sharma.

  • Posted 14 April 2020, 3:14 am EST

    Hi Prabhat,

    The fault severity was the reason behind asking you, “how long this issue is known to your developers and when expected to be resolved”.

    This very serious fault or defect in a computer program should have been taken on top of the top priorities because no any end-user-developer would check the length of the numeric value beyond 15 and assumes everything will be OK.

    It’s a request to imagine the impact of the wrong result. It could be very expensive.

    Regards

    Mahesh

  • Posted 15 April 2020, 8:32 pm EST

    Hi Mahesh,

    We understand your concern.

    Our developers are working on this issue at the priority and it will get fixed in the next release i.e. 2020V1 HotFix.

    [Internal Tracking ID: 422953]



    Regards,

    Prabhat Sharma.

  • Posted 4 July 2020, 4:09 pm EST

    Hi,

    This issue has been fixed in the latest hotfix builds i.e. 4.5.2.20201.424 and you can use the builds in your application to resolve the problem that you are getting at your end.

    You can upgrade the builds via latest ComponentOneControlPanel utility by following below given steps:

    1: Run the utility.

    2: Go to the UPDATE tab under the PRODUCTS tab.

    3: Check the option: Include prerelease and hotfix versions.

    4: Expand WinForms and click the update button.

    Regards,

    Prabhat Sharma.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels