Excel Export Crash

Posted by: patrick.muellner on 25 September 2023, 5:27 am EST

  • Posted 25 September 2023, 5:27 am EST

    Please take the whole description from the pdf.

    RegardsTestApp.zipProblem description.zip

  • Posted 26 September 2023, 3:38 am EST

    Hello Patrick,

    Apologies for the inconvenience caused.

    As 4.0/2.0 FW controls are in maintenance mode and out of support, so we request you to try out our 4.5.2 FW / 4.8 FW controls and let us know if you face the same issue with it also.

    If the same issue occurs with it, please share your OS details with the version so that we can test it in the same environment.

    Regards,

    Prabhat Sharma.

  • Posted 26 September 2023, 4:32 am EST

    Hi Patrick,

    could you try to add this to your “SaveExcel” call?

    grdTest.SaveExcel (filename, ..., FileFlags.IncludeFixedCells or FileFlags.VisibleOnly or FileFlags.OpenXml)

    The latter is required to save the grid as “xslx”. I don’t know if there is code to autodetect this based on the file extension.

    Hope this helps

    Wolfgang

  • Posted 27 September 2023, 2:15 am EST

    Hi,

    sorry also doesn’t works.

    Any other idea? Problem is, that we can’t change so quickly the whole Framework.

    Regards

  • Posted 27 September 2023, 3:42 am EST

    You could use the same workaround that we used since ages due to performance reasons - a long time ago, we noticed that saving a C1FlexGrid to a “\tsclient.…” path was poorly slow. Don’t know whether this still applies, but the following workaround still exists in our code ;-). Maybe that’s also the reason that we never run into the bug that hit you.

    So, in case the path starts with "\tsclient", we first save C1FlexGrid to the temp directory, and then copy the resulting file to the tsclient target path.

    Could you try to apply this to your code, too?

    Best regards

    Wolfgang

  • Posted 29 September 2023, 12:02 am EST

    Hello Patrik,

    Can you please try the workaroud suggested by Wolfgang and see if it helps.

    **>>Any other idea? Problem is, that we can’t change so quickly the whole Framework.

    **

    Migrating to 4.5.2/4.8 FW controls can be done using a few simple steps as suggested here:

    https://www.grapecity.com/blogs/how-to-migrate-to-net-framework-4-8-using-componentone

    In the meantime, please share the asked OS details with version and stripped-down sample where you are facing this issue so that we can create the similar setup at our end and assist you further accordingly.

    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